[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: proposed patch for Bison core dumps when using lalr1.cc
From: |
Tim Van Holder |
Subject: |
Re: proposed patch for Bison core dumps when using lalr1.cc |
Date: |
Sat, 1 Mar 2003 23:12:48 +0100 |
> Paul> Admittedly the simple cases are not as popular these days.
> Paul> Still, they are in use, and the longstanding tradition
> is to write a
> Paul> header file only if -d is specified.
>
> Paul> It would be confusing for users if C and C++ behaved
> Paul> differently here.
>
> I don't think so. Generating C without headers belongs to the past.
> Except for yacc.c, I believe all the other skeletons can generate
> mandatory headers.
I disagree - there's something icky about a tool generating files
I didn't request - if I tell bison to make me a grammar in foo.cc
from foo.yy I do not expect to get 3 header files generated for me
as well - especially if that list of additional files is not stable
across bison versions (and I suspect that will be the case, especially
for skeletons that evolve).
At the very least bison should provide an option (--clean?) that cleans
up after itself properly.