Re: LRSTAR 3.0: LALR(k) parser generator & lexer generator for C++

Hans Aberg <haberg-news@telia.com>
Thu, 09 Feb 2012 10:28:30 +0100

          From comp.compilers
Related articles
LRSTAR 3.0: LALR(k) parser generator & lexer generator for C++ paul@paulbmann.com (Paul B Mann) (2012-02-07)
Re: LRSTAR 3.0: LALR(k) parser generator & lexer generator for C++ sgk@REMOVEtroutmask.apl.washington.edu (Steven G. Kargl) (2012-02-08)
Re: LRSTAR 3.0: LALR(k) parser generator & lexer generator for C++ haberg-news@telia.com (Hans Aberg) (2012-02-09)
Re: LRSTAR 3.0: LALR(k) parser generator & lexer generator for C++ paul@paulbmann.com (Paul B Mann) (2012-02-10)
Re: LRSTAR 3.0: LALR(k) parser generator & lexer generator for C++ paul@paulbmann.com (Paul B Mann) (2012-02-10)
Re: LRSTAR 3.0: LALR(k) parser generator & lexer generator for C++ sgk@REMOVEtroutmask.apl.washington.edu (Steven G. Kargl) (2012-02-11)
Re: LRSTAR 3.0: LALR(k) parser generator & lexer generator for C++ gah@ugcs.caltech.edu (glen herrmannsfeldt) (2012-02-12)
Re: LRSTAR 3.0: LALR(k) parser generator & lexer generator for C++ paul@paulbmann.com (Paul B Mann) (2012-02-14)
Re: LRSTAR 3.0: LALR(k) parser generator & lexer generator for C++ boriel@gmail.com (Boriel) (2012-10-24)
[9 later articles]
| List of all articles for this month |
From: Hans Aberg <haberg-news@telia.com>
Newsgroups: comp.compilers
Date: Thu, 09 Feb 2012 10:28:30 +0100
Organization: A noiseless patient Spider
References: 12-02-004 12-02-006
Keywords: C, code
Posted-Date: 10 Feb 2012 23:17:15 EST

On 2012/02/08 20:08, Steven G. Kargl wrote:
> 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.


Except OS X, which is certified UNIX in versions 10.6 and later. (Though
one can choose a case sensitive file system, some software, notably from
Adobe, will not run properly.)


> 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"'.


As long the file is not called differently, this is not so a big problem
- just change the file name.


Hans


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.