Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!gatech!gt-eedsp!baud
From: baud@gt-eedsp.gatech.edu (Kurt Baudendistel)
Newsgroups: comp.lang.c++
Subject: Re: libg++ and copylefts
Message-ID: <329@gt-eedsp.gatech.edu>
Date: 19 Jul 89 12:36:37 GMT
References: <2053@dataio.Data-IO.COM> <6590203@hplsla.HP.COM> <904@accuvax.nwu.edu> <914@accuvax.nwu.edu>
Reply-To: baud@gt-eedsp.UUCP (Kurt Baudendistel)
Organization: Georgia Institute of Technology
Lines: 22

In article <914@accuvax.nwu.edu> morrison@accuvax.nwu.edu (Vance Morrison ) writes:
>After following this discussion of copylefts and listening to a lot of
>people rant at the evil of the copyleft, it occures to be there is a
>very simple solution to the problem[: distribute your code as object to
>be linked with gnu code].

This sounds great, but it won't work for libg++ since this library is and
must be distributed in source form.

However, we've heard rumors of gnu work on ways to pre-compile header
files to promote faster compilation. This is desirable, since in many
applications, the parsing of class definitions takes lots of time.

But how will this affect the copylefting of libg++? Will we be able
to use Vance's scheme for libg++ in pre-compiled form? And when will
such a facility be available?

kurt
-- 
Kurt Baudendistel --- GRA
Georgia Tech, School of Electrical Engineering, Atlanta, GA  30332
internet: baud@eedsp.gatech.edu         uucp: gatech!gt-eedsp!baud