Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!hplabs!hp-pcd!hplsla!jima
From: jima@hplsla.HP.COM (Jim Adcock)
Newsgroups: comp.lang.c++
Subject: Re: g++ vs. cfront 2.0 in the Real World
Message-ID: <6590190@hplsla.HP.COM>
Date: 10 Jul 89 17:50:50 GMT
References: <799@redsox.bsw.com>
Organization: HP Lake Stevens, WA
Lines: 15

>This is not entirely correct.... As with GCC, you can use the G++
>*compiler* to compiler your code into binary, without having to
>release the source code.  However, if you include the source or object
>code from the libg++ libraries (stream.h, Strings,h, etc.) with your
>product, then your work falls under the copyleft.

I've heard this before, but I've yet to see Stallman verify this in black and
white terms.

In any case, if one is doing commercial development on *anybodies* compiler
one would be best served to review what one is doing with a competent
software/copyright lawyer to make sure you're "dotting all you I's, and 
crossing all your T's."  Witness recent major software lawsuits.  It seems
really unclear in software nowadays when a work is a derived work, and when
it isn't.  Better safe than sorry.  Hate to have to get lawyers involved tho'..