Path: csiph.com!x330-a1.tempe.blueboxinc.net!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!news.glorb.com!usenet.stanford.edu!news.iecc.com!nerds-end From: "Steven G. Kargl" Newsgroups: comp.compilers Subject: Re: LRSTAR 3.0: LALR(k) parser generator & lexer generator for C++ Date: Wed, 8 Feb 2012 19:08:18 +0000 (UTC) Organization: A noiseless patient Spider Lines: 16 Sender: johnl@iecc.com Approved: comp.compilers@iecc.com Message-ID: <12-02-006@comp.compilers> References: <12-02-004@comp.compilers> NNTP-Posting-Host: news.iecc.com X-Trace: leila.iecc.com 1328728571 13984 64.57.183.58 (8 Feb 2012 19:16:11 GMT) X-Complaints-To: abuse@iecc.com NNTP-Posting-Date: Wed, 8 Feb 2012 19:16:11 +0000 (UTC) Keywords: LALR, code Posted-Date: 08 Feb 2012 14:16:11 EST X-submission-address: compilers@iecc.com X-moderator-address: compilers-request@iecc.com X-FAQ-and-archives: http://compilers.iecc.com Xref: x330-a1.tempe.blueboxinc.net comp.compilers:446 On Tue, 07 Feb 2012 14:47:17 -0800, Paul B Mann wrote: > No one has ported it to Unix or Linux yet. It may be 99% portable. > It was written with Microsoft Visual > Studio 2008 C++, however, I try to make my code portable. UNIX and unix-like system are case sensitive. There is no chance that this code will build without a significant porting effort. For example, you have Global.H in some directory; yet, your source has '#include "global.h"'. It may also be advantageous to include simple instructions of which files need to be compiled and the order. -- steve