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

"Steven G. Kargl" <sgk@REMOVEtroutmask.apl.washington.edu>
Sat, 11 Feb 2012 18:31:29 +0000 (UTC)

          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)
Re: LRSTAR 3.0: LALR(k) parser generator & lexer generator for C++ patchell@cox.net (Jim Patchell) (2012-11-05)
Re: LRSTAR 3.0: LALR(k) parser generator & lexer generator for C++ charlesb.cca@mpowercom.net (Charles E. Bortle, Jr.) (2012-11-12)
Re: LRSTAR 3.0: LALR(k) parser generator & lexer generator for C++ charlesb.cca@mpowercom.net (Charles E. Bortle, Jr.) (2012-11-12)
[4 later articles]
| List of all articles for this month |

From: "Steven G. Kargl" <sgk@REMOVEtroutmask.apl.washington.edu>
Newsgroups: comp.compilers
Date: Sat, 11 Feb 2012 18:31:29 +0000 (UTC)
Organization: A noiseless patient Spider
References: 12-02-004 12-02-006 12-02-009
Keywords: tools, C++
Posted-Date: 12 Feb 2012 01:17:05 EST

On Fri, 10 Feb 2012 13:24:41 -0800, Paul B Mann 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 have created a newer release: 3.0.211 in which I renamed the file
> names to all lower case and changed the #include filenames to match.
>
> I also added "readme.txt" files to the "source" directories which
> tells you how to compile under UNIX/Linux (i.e. compile the
> "lrstar.cpp" file, the "dfastar.cpp" file and the "dfac.cpp" file).
>
> I'm sure there will be more changes needed, because I'm not so
> familiar with UNIX.


Thanks.


Yes, more changes are needed. First, one needs to comment out
'#define DOS' in globals.h. Then, (on at least FreeBSD) one needs to
remove '#include "malloc.h", because everything that at one time was
declared in that file is now found in stdlib.h and inclusion of
malloc.h leads to an error. Now, I hit the show stopper:


laptop:kargl[240] g++ -o z -I. dfac.cpp |& more
In file included from actions.cpp:4,
                                  from dfac.cpp:2:
global.h:52:15: error: "or" cannot be used as a macro name as
it is an operator in C++


--
steve


Post a followup to this message

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