[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: error-tokens and locations?

From: Ian Badcoe
Subject: Re: error-tokens and locations?
Date: Tue, 18 Nov 2003 20:04:05 +0000

Here are the files, which should be small enough not to need compressing.

I did try to tar and compress them but after 10 minutes squinting at the rather odd tar documentation I gave up. Once upon a time I would have known, sigh.

They should be pretty platform independent, except maybe for some LRCF conversion.

The makefile is totally primitive. "make all" will build it into the compiler's default output name.

I may have left an absolute path to bison in there, which you'll want to change to your development version.

        temp.txt is the output I got from bison-1.875c under cygwin.

The error is apparent in the first MERGING LOCATIONS line, where the [0] is the num parameter passed to the macro.

"make check.txt" is the output of make check run on bison-1.875c, but it's probably more to do with the invocation problems than the interesting bug.

        If it won't build, let me know and I'll think again.

        Ian B

At 14:18 17/11/2003 -0800, Paul Eggert wrote:
Ian Badcoe <address@hidden> writes:

> have I confused you between the original locations bug and the
> coincidental crash bug that I got when I started building 1.875c?

Yes, I guess so.

> do you mean that you tried my test-program on another system
> and the problem did not recur?

No, I haven't done that.  Sorry, I've forgotten your test case (it
isn't archived on
yet).  Is it a test case that should be portable to Linux?
If so, please resend it.

Attachment: temp.txt
Description: Text document

Attachment: LLP_Support.h
Description: Text document

Attachment: LowLevelParser.l
Description: Text document

Attachment: LowLevelParser.y
Description: Text document

Attachment: make check.txt
Description: Text document

Attachment: makefile
Description: Binary data

Attachment: LLP_Support.cpp
Description: Text document

Free transport into the future, while you wait.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]