Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!swrinde!ucsd!dog.ee.lbl.gov!daffy.ee.lbl.gov!vern
From: vern@daffy.ee.lbl.gov (Vern Paxson)
Newsgroups: comp.sources.wanted
Subject: Re: YACC++ LEX++
Message-ID: <8676@dog.ee.lbl.gov>
Date: 18 Dec 90 21:46:10 GMT
References: <5140@tahoe.unr.edu> <3706@atomic.trl.mei.co.jp>
Sender: usenet@dog.ee.lbl.gov
Reply-To: vern@daffy.ee.lbl.gov (Vern Paxson)
Organization: Lawrence Berkeley Laboratory, Berkeley
Lines: 22
X-Local-Date: Tue, 18 Dec 90 13:46:10 PST

In article <3706@atomic.trl.mei.co.jp> ntanaka@trl.mei.co.jp (Nobuaki Tanaka) writes:
> [rebecca@unssun.nevada.edu (Rebecca Hayhurst), <5140@tahoe.unr.edu>]:
>  | I'm looking for information, source on a LEX and YACC to produce
>  | C++ code.  
> ...
> I'm also interested in YACC++ and LEX++. Would anyone explain about
> those tools in this News Group?

On the lex side of things, flex is a freely available version of lex which
produces C++-compatible code (and you can write your actions in C++ if you
want).  You can get it via anonymous ftp to ftp.ee.lbl.gov (128.3.254.68;
retrieve flex-2.3.tar.Z, using binary mode, and any flex-2.3.patch-X files
you see, using ascii mode) or from the comp.sources.unix archives.

If you don't have anonymous ftp or comp.sources.unix access, let me know
and I'll mail you the uuencoded tar file.

		Vern

	Vern Paxson				vern@helios.ee.lbl.gov
	Real Time Systems			ucbvax!helios.ee.lbl.gov!vern
	Lawrence Berkeley Laboratory		(415) 486-7504