I cringed so hard at the "Tiny, easily worked around torque script issues don't really effect anyone at all." Are you serious? These are things people have been begging for, for ages and you call them "Tiny easily worked around issues." Then why dont you just do it? You said it yourself these are tiny easily worked around issues. We could code so much more with the small change of making the NULL character available in strings, and had access to better integer modification. And then we could better utilize Steam Workshop.
I honestly can't believe that you are arguing this. Not that the argument itself is absurd, I'd expect it out of a newbie coder that doesn't understand how the engine or language works, but that
you are making this argument. How do you seriously have that little of an idea how Torque works? I mean, this is coming from me, the person who is actively trying to integrate JavaScript with Torque to provide a more well rounded and complete coding experience, but you're still batstuff insane. The only situation where you even have to deal with \x00 bytes in strings is when you're downloading binary files-- I have two solutions for you: one - use
TCPObject::setBinary(1); and
TCPObject::saveBufferToFile( file ) two - send the file through your own webserver to be parsed and send the clean output to Torque. Get creative. You can't expect Badspot to replace the use of c-strings in his language with some other form of strings simply to support you misusing the string system. Torque is, surprisingly, a very well written language. It's not on par with JavaScript and other extremely popular languages, but for what it is it's really well written. You can't just disassemble it and change things without breaking everything.
