home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!uwm.edu!ogicse!das-news.harvard.edu!cantaloupe.srv.cs.cmu.edu!ddj
- From: ddj+@cs.cmu.edu (Doug DeJulio)
- Newsgroups: gnu.misc.discuss
- Subject: Re: Dylan supported by GNU in future ?
- Message-ID: <BzEx1F.11s.2@cs.cmu.edu>
- Date: 17 Dec 92 16:41:38 GMT
- Article-I.D.: cs.BzEx1F.11s.2
- References: <F7LVVB14w165w@mantis.co.uk> <1gnu87INNguv@uwm.edu> <1992Dec16.220835.2973@netcom.com>
- Sender: news@cs.cmu.edu (Usenet News System)
- Organization: School of Computer Science, Carnegie Mellon
- Lines: 14
- Nntp-Posting-Host: itc.cs.cmu.edu
-
- In article <1992Dec16.220835.2973@netcom.com> jimlynch@netcom.com (Jim Lynch) writes:
- >Not so: you must add to this category any code that uses Bison; this is an
- >example of the author wanting _all_software to be free. If I write my own
- >parser, can I use bison _just_ to generate the parse tables (and do what I
- >want with the result?)
-
- Yeah. The reason you have to GPL Bison output currently is that the
- skeleton file is included in the output, and that skeleton file is
- covered by the GPL. If you modify Bison so that it just outputs
- tables and doesn't include the skeleton, or if you write from scratch
- your own skeleton files, that restriction should go away.
- --
- Doug DeJulio
- ddj+@cmu.edu
-