Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!apple!ames!mailrus!bbn!mit-eddie!uw-beaver!uw-june!pardo From: pardo@june.cs.washington.edu (David Keppel) Newsgroups: comp.lang.misc Subject: Re: increasing yacc states Message-ID: <8704@june.cs.washington.edu> Date: 12 Jul 89 15:13:52 GMT References: <6244@goofy.megatest.UUCP> Reply-To: pardo@uw-june.cs.washington.edu (David Keppel) Organization: University of Washington, Computer Science, Seattle Lines: 36 djones@megatest.UUCP (Dave Jones) writes: >[Does anything compiled with BISON need to say `BISON' on startup?] >[Must anything compiled with BISON be shipped with the GNU baggage?] I am not a lawyer, nor an employee of the free software foundation. What follows is only my understanding. The following applies ONLY TO PROGRAMS THAT ARE BEING DISTRIBUTED. Anything that is used strictly by you can follow any rules you like. * The GNU rules require that any *interactive* GNU software name itself and reference the GNU copyleft when it is started. Thus, GNU emacs must name itself (expert users can turn this off, if desired) and GNU cc (gcc) need not. * `Anything compiled with BISON' means two things. BISON is approximately a filter that takes TWO input files and produces an output file. One of the files that is normally included is a skeleton file written by GNU. That skeleton file is copylefted and appears in the output. Thus, the output is a `derived work'. If you use the default skeletons, then any code that is derived from or linked with the BISON output must follow the terms of the GNU copyleft. If you use your own skeleton, then you need not follow the GNU copyleft. If you build a parser using a standard BISON skeleton and then link it to a program that you distribute, then the sources FOR THE ENTIRE PROGRAM must be freely distributable. If you create a `.o' file for the parser and do NOT link it in -- the recipient must link it in -- then only the source for the parser must be freely distributable. That's my understanding. ;-D on ( Interesting GNU statements ) Pardo -- pardo@cs.washington.edu {rutgers,cornell,ucsd,ubc-cs,tektronix}!uw-beaver!june!pardo