[Top][All Lists]

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

Re: CVS Bison (2002-10-20) creates empty structures and initializers

From: Akim Demaille
Subject: Re: CVS Bison (2002-10-20) creates empty structures and initializers
Date: 23 Oct 2002 09:14:27 +0200
User-agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Honest Recruiter)

| > From: Akim Demaille <address@hidden>
| > Date: 22 Oct 2002 10:33:45 +0200
| > 
| > I'm not sure how to solve this issue.  I'm not fond _at all_ of
| > conditionalizing all the code that uses locations :(
| This indicates a bit of a shortcoming in our current technology, as it
| should be easier to conditionalize things like that.
| I am thinking of suggesting that we go back to using the C
| preprocessor to conditionalize C code, at least when this is easy.

I was not speaking about how easy it could be, I was merely referring
to the pollution of the skeleton, be it M4 pollution, or CPP

| With the C preprocessor, one can decide at C-compile-time (rather than
| at Bison-compile-time) whether to enable or disable a conditional
| feature. 

I fail to see how this can be a real feature.

| Also, it's easier for non-M4 programmers to follow what's going on.

But people trying to copy-cat a CPP skeleton for a CPP-less language
will fail.  So I'm still an M4 fan here.

reply via email to

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