On Wed, Feb 11, 2015 at 3:27 AM, Ulya Fokanova <skvad...@gmail.com> wrote: > Well, you almost convinced me. > I didn't realize that re2c users are so strongly against > trivial code changes.
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. > As for imaginary conflicts, I saw a real one when at some > point I tried to add name "YYEOF". 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 ------------------------------------------------------------------------------ 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
