One thing that's generally accepted is that a strict EUO-->Lua convert would be impossible. Since Lua cannot loop with goto and has no facility to "continue" from a looping construct, then it's difficult to reconstruct the original execution intention.
What will work is an interpreter that's written in Lua. That's already been started by Cheffe. That project just needs some traction.
Hence why no one should ever use GoTo's or Break/Continue! I believe I've written a few posts about this!! Poor programming habits will always come back to bite you!!
As for TopTwo's view, I believe what he's trying to convey is that by now, we're all practically in a common law marriage with EUO. It's like the one who owns the house has been saying "You know, I think we should move to (insert some far away place here)" and you say "Eh, I don'y really wanna move there" and you have these conversations over a couple years, and one day, you come home and there's a note in chalk on the sidewalk saying "Hey! I sold the house and moved! You can come join me if you want to!"
I think we can all agree that that kind of behavior is totally uncalled for and downright hurtful if you truly cared about the other person. That's all I'm going to say on that topic.
As for myself, I have barely had time to maintain my current scripts and have tons of features I still wish to add to them. In the last 3 years I've learned C, C++, C#, Java, Verilog, MATLAB, SQL, PHP, ASP.NET, and am currently learning Objective-C. I simply do not have time to confuse myself with one more language, especially one as different from the rest as Lua.
I am honestly more inclined to learn about client interaction and write my own version of EasyUO that would support the EUO language as well as fix the numerous outstanding errors, possibly even working with TM to make it SUO compatible. I will not have time for a project of that scope until next summer, so I will be back then to re-evaluate.
