"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.
New input API <http://skvadrik.github.io/aleph_null/posts/re2c/2015-01-13-input_model.html>will introduce some new user-exposed names.
At first I suggested these names: YYPEEK YYSKIP YYBACKUP YYBACKUPCTX YYRESTORE YYRESTORECTX YYHASbut after some discussion on the mailing list <https://www.mail-archive.com/re2c-general@lists.sourceforge.net/msg00243.html>(read the
whole thread) we decided to change names: RE2C_PEEK RE2C_SKIP RE2C_BACKUP RE2C_BACKUP_CTX RE2C_RESTORE RE2C_RESTORE_CTX RE2C_HAS It's clear that "RE2C_" has always been a proper prefix. Breaking backward compatibility is bad, but we'll have to do it at some point. In a rapidly developing project I would first add a switch "--new-names" and after some two releases (when everybody migrates successfully) substitute is with "--old-names", but re2c users show up too rarely and the usual migrating scheme makes no sense. Note that re2c users will have to either use switch "--old-names" (and modify build scripts) or make a trivial fix of source code, but not both.
------------------------------------------------------------------------------ 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
