On Mon, 4 Dec 2006, Jeff Inman wrote: > > I meant to ask: does this sound like it will address your needs? > > Thanks for your reply. Yes, these sound like they will more than > solve my problem. I can use a manual (and your message) to help > me remember which is which
Currently in CVS, I've added a manual section dedicated to these directives. It details their usage and the problems with %{...%} that they solve. I hope it can serve as a single reference point to help you remember them. > , but if your design is still flexible, I'd suggest > using names that are more obvious about where the code will be > generated. For example: > > %header{...} > %both{...} > > Or maybe: > > %declare{...} > %define{...} > %both{...} In test release 2.3a, the directives are actually named %before-header, %start-header, %end-header, and %after-header. When considering C and C++ in isolation, I preferred those names although other developers seemed to find them confusing. However, we have someone working on adding Java support, and there could be other target languages some day as well. We chose the current names (%code, %requires, etc) because they describe the purpose of the directives at a more abstract level that seems to make sense for Java and hopefully future languages. > But, whatever they are called, these will be welcome additions. > Thanks. Great. Thanks for the feedback. After the next release when you've had a chance to use these, we'd be glad to hear your experiences. I hope we can roll a test release some time soon so interested users can try these out, but I don't make that decision. _______________________________________________ help-bison@gnu.org http://lists.gnu.org/mailman/listinfo/help-bison