From: Mighty Jo <mig...@gm...> - 2015-12-05 02:26:23
|
Good evening folks, I've been working on overhauling the scanner generation code to move all of the target language emissions into the skeleton. I don't know yet whether the state tables can be generalized this way, but I've identified a few dozen sites where C code emissions can be converted to setting m4 definitions and performing checks in the skeleton. In the skeleton itself I've found similar checks coded two ways. One is the collection of m4_check_something macros. The other is the set of %check_something statements which are translated into m4 macro calls by skelout(). Which style do you prefer going forward? I won't remove either of them in my work, but I have to augment at least one of them and I'd like to know the community's thoughts. -Joe |