From:	Chris Croughton <crough45 AT amc DOT de>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: DJGPP, Bison and... Lex?
Date:	Tue, 30 Jun 1998 10:14:01 +0200
Message-ID:	<35989E49.C6D@amc.de>
References:	<3 DOT 0 DOT 5 DOT 32 DOT 19980630094748 DOT 007aba00 AT pop DOT uow DOT edu DOT au>
NNTP-Posting-Host:	bob.bob.bofh.org
MIME-Version:	1.0
Lines:	29
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Brett Porter wrote:

>         However, I was wondering if anyone knows where I can get a version of Lex
> that can be used in conjunction with Bison in case mine doesn't work out.

ftp://ftp.simtel.net/pub/simtelnet/gnu/djgpp/v2gnu/flx*.zip

Or mirrors.  I assume that what you missed is that the GNU version of
lex is called 'flex' and is archived in file with name 'flx*' rather
than 'lex*'.

>         Also, can someone in the know clarify the copyright issues here: both
> Bison and possibly a modified version of the C preprocessor will be used in
> the script compiler, but the compiler will not be commercially released. It
> will be used to create data that (hopefully!) may be commercially released.
> Is this all ok? I'm using Bison 1.25 which has the exception included about
> the parsing code, but it shouldn't make a difference anyway because neither
> pieces of code are actually in the distributed product.

Code generated with bison/yacc/flex/lex has no licensing problems
because of that using them.  Both the original yacc/lex authors and the
GNU versions have been careful to keep it that way, because there are a
lot of people depending on them for their commercial products.  So
(absent other restrictions) you are free to distribute your compiler any
way you want, and anything your compiler generates is totally free for
you to do whatever you want with it (GPL etc. don't apply to the output
of programs).

Chris C

- Raw text -