On Wed, 31 May 2006, Akim Demaille wrote: > If you wish :) I was also considering the time of recompilation of > the file itself. Maybe I'm biased: I'm using this approach in a C++
OK, I get it... especially for C++. > Maybe that's overkill for Bison Well, maybe in the short term, but.... >, in which case your approach is simpler. Not by much. I'll go with your approach since it's more scalable... and I've already done it anyway. > > I was going to name them "changelog-id.h", "changelog-id.c", "const char > > I meant changelog-id. Anyway, I personally use revision.c ;) Now I don't like "changelog-id". The current use of the ChangeLog Id for the revision is a detail that could potentially change. The most important thing about this variable is that it's the Bison "revision". Unless there are objections, I'll apply my updated patch after 2.3 is out. Joel
