Patches are frustrating things to apply, since they are necessarily highly version dependent and they often don't compose - the chances of two lexer patches conflicting are quite high.
This is the main reason I'm still hesitating to post any of my various hacks on the power patch page. I'm convinced that, if you're going to use exactly one syntax mod, the one to pick is Peter's table unpack patch. Any of my mods really ought to be your second patch, at best, meaning that a 5.2 diff file is going to be less than ideal.
Perhaps I will make a selected set of Useful Patches available as options in LuaBuild.
Yes -- this seems to be the more natural way to do it. I've been thinking about posting a bundled "sven's patch set" to the wiki -- at the moment it would probably include table unpack, increment, and safe table navigation.
I'm still waffling about whether or not to throw my stringifiction patch in the mix as well. It is an unapologetic one-trick pony, but its an important trick, and one I've been using it a lot. Yet when the syntax really starts to proliferate, the language stops feeling like Lua. It's still a nice scripting language, but, it's also unquestionably more dense and obscure.
The wiki page states that if a patch changes syntax or semantics, the resulting scripting language should not be called "Lua". I've been resisting the need to rename my own scripting language-- telling myself that most everything I've done is modest enough to not really demand a new name. (And as long as I'm working in the context of a solo personal project, language names are academic.) But I think stringification may be my Rubicon.
-Sven