There are a lot of code bases that are in production use and wary
about changes of this sort, especially when it's something like
lexer/parser logic which can be a bit of a handful to understand in
the first place.  If it *doesn't* "just work" for whatever reason
fixing it may be a bit daunting, especially if the guy who wrote the
original lexer/parser code retired five years ago and no one on the
current team knows anything about it.
I see.

So for now, 2:0 in favor of old names.
This may or may not make any sense, but what about the following as a
possibility?

Have a --names_prefix option that, rather than hard coding old (yy/YY)
or new (re2c/RE2C) options, allows a user specified choice?  Default
to yy/YY still, since that's the prevalent style in other tools and
codebases, but allow any particular user to override (--names_prefix
re2c, for example, would replace yy with re2c and YY with RE2C) if
they have a situation where the deciding factor is avoiding conflicts
rather than external compatibility.

Would that be a practical option?

Cheers,
CY
The thing is, re2c allows to override each particular name
(or at least its prefix)using inplace configurations, e.g:

   re2c:define:YYCURSOR= <new name>;
   re2c:labelprefix = <new prefix>;
   re2c:label:yyNext= <new name>;
   re2c:variable:yyaccept= <new name>;

So the main point was more of a "global name unification",
but if it's that bad, I'll just add inplace configurations
for new names:

   re2c:define:YYPEEK
   re2c:define:YYSKIP
   re2c:define:YYBACKUP
   re2c:define:YYBACKUPCTX
   re2c:define:YYRESTORE
   re2c:define:YYRESTORECTX
   re2c:define:YYLESSTHAN

Still waiting for other re2c users' opinions. :)

Ulya
------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Re2c-general mailing list
Re2c-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/re2c-general

Reply via email to