Re: bison 1.29 bug+lack

[wwp]

Hi there,

On 31 Oct 2001 12:59:35 +0100, Akim Demaille scribbled:
> Huh?  Hm, I lost your file, could you send it again?  Thanks!

Arg, sorry _I_ forgot to attach the file (as usually). Now tis OK.

Using bison 1.30 (from .tgz):
- running 'bison -d 9foo.y' will raise the macro name non-compliance bug.
- running 'bison foo.y' will raise the .y parsing segfault.


> subscript> - Bison still produces non-compliant C code when parsing
> subscript> filenames whose 1st char is numerical ( for instance:
> subscript> 'bison 9foo.y').
> 
> Heck.

:))


> subscript> As I shown in a previous email, It's quite easy to fix the
> subscript> 2nd point.
> 
> Indeed, prepending something, such as bison, would be fine.  Again, a
> simple question: this is actual code, or you find it reading the code?

I'm afraid I don't understand what you mean!


Best regards

-- 
wwp

9foo.y
Description: Binary data

foo.y
Description: Binary data