> On 10 Feb 2015, at 23:16, Ulya Fokanova <skvad...@gmail.com> wrote: > > "YY" prefix comes from yacc-family parser generators. > re2c is often used in pair with these parser generators, > so there's a possibility of name collisions.
Not only yacc, but also scanners like f/lex follows that same tradition and name variables YYVAR. I have never seen a "name-space” conflict with bison/yacc/byacc and re2c. I understand why you want to have a separate “name-space” for re2c variables, but it is not broken now. However, changing the naming scheme _will_ break code and require rewrites or configure changes. The argument that "there's a possibility of name collisions” is rather thin for breaking an “API” interface IMHO. Any old project using re2c will break on systems with the new re2c. So if you absolutely must do this change it is better to make a "--new-names” switch instead so the default is backward compatibility. ------------------------------------------------------------------------------ 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
