sem_names.h needs to be generated only when sem_enum.h is changed, which is not often. Why bother doing it for each build? John On Wed, Jun 18, 2014 at 05:10:24PM +0200, Christian Egli wrote: > On 06/18/2014 03:33 PM, John J. Boyer wrote: > >A note on semantic actions. sem_names.h is a generated file. The basic > >file is sem_enum.h . If you add a semantic action you must do it in > >sem_enum.h and then run Makesemnames to generate sem_names.f . > >Descriptive comments should be in sem_enum.h . It already contains > >comments on various classes of semantic actions.Of course this is just > >source code documentation. > > This is something that has been bugging me forever and tree days. > Why do we need both these files? Presumably we need both of them. If > so then could we not generate the other one based on a simple Perl > script that is integrated with the build system? I looked at > make_sem_names.c. Am I right in my conclusion that it simply takes > all the names from the enum and produces the semNames array? Maybe > this could even be done with a preprocessor macro (hmm, on second > thought probably not)? > > I'll spend a few minutes to cook up a script to do this. > > Thanks > Christian > > -- > Christian Egli > Swiss Library for the Blind, Visually Impaired and Print Disabled > Grubenstrasse 12, CH-8045 Zürich, Switzerland > > > ----- > Tag der offenen Tuer: Die SBS laedt Sie herzlich ein: 28. Juni 2014 > von 9 bis 16 Uhr. Mehr Informationen erhalten Sie unter > http://www.sbs.ch/offenetuer > For a description of the software, to download it and links to > project pages go to http://www.abilitiessoft.com -- John J. Boyer; President, Chief Software Developer Abilitiessoft, Inc. http://www.abilitiessoft.com Madison, Wisconsin USA Developing software for people with disabilities For a description of the software, to download it and links to project pages go to http://www.abilitiessoft.com