Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.chainon-marquant.org!nntpfeed.proxad.net!proxad.net!feeder1-1.proxad.net!198.186.194.247.MISMATCH!news-out.readnews.com!transit3.readnews.com!nx02.iad01.newshosting.com!newshosting.com!216.196.98.142.MISMATCH!border3.nntp.dca.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!news.iecc.com!nerds-end From: Paul B Mann Newsgroups: comp.compilers Subject: Re: LRSTAR 3.0: LALR(k) parser generator & lexer generator for C++ Date: Fri, 10 Feb 2012 10:19:37 -0800 (PST) Organization: Compilers Central Lines: 22 Sender: johnl@iecc.com Approved: comp.compilers@iecc.com Message-ID: <12-02-008@comp.compilers> References: <12-02-004@comp.compilers> <12-02-006@comp.compilers> NNTP-Posting-Host: news.iecc.com X-Trace: leila.iecc.com 1328933875 48415 64.57.183.58 (11 Feb 2012 04:17:55 GMT) X-Complaints-To: abuse@iecc.com NNTP-Posting-Date: Sat, 11 Feb 2012 04:17:55 +0000 (UTC) Keywords: C, tools, comment Posted-Date: 10 Feb 2012 23:17:55 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:448 On Feb 8, 1:08 pm, "Steven G. Kargl" wrote: > > 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. I can rename those header files and do a global change on the include filenames in Visual Studio in about 15 minutes. Is it really that difficult to do this with UNIX ? I will make sure the next release has these changes. Thanks for the valuable feedback. I really appreciate it. Paul B Mann [It's easy enough if you know what the files are and where all the include statements are. -John]