You guys need to take a step back and look at the big picture here. Tiny, easily worked around torque script issues don't really effect anyone at all.
Spend a day or two of your time dedicated to fixing two things: low precision numbers and null bytes in strings; and you will have already fixed countless bugs and added endless possibilities to the language, which in turn would have a major effect on everyone.
Dislike how your bls saves take up MEGABYTES each for reasonably sized builds? One could easily write a compressor for it and it would only take up a few hundred kilobytes; wonderful for transporting your saves to other users and easily implemented directly into the saving GUI.
That's just one example, there are endless possibilities that simply revolve around being able to use the null character.
Another possibility is uploading both a save and a picture along with it to a save hosting service like the one RTB was planning, and in-game addon uploading.
Using doubles and int64s would solve a few pretty annoying glitches. Doubles would get rid of many glitches involving brick collision, like being able to jet upwards through bricks if you're high up in the air (Like at Red_Guy's server), and it's also possible that it would fix the corner jumping glitch as well.
The problem is that the cool content that is already created never gets into the hands of players. SCP containment breach, cool how do I play that? Titanic build - cool, how do I see that? What about that awesome castle someone made once, you know that one? Oh that guy who made it died and took all his save files with him? Ok. This is the problem.
This is what RTB was GOING to be for. Now it's dead.
Step 1: http://en.wikipedia.org/wiki/Null-terminated_string
Step 2: http://www.youtube.com/watch?feature=player_detailpage&v=GlKL_EpnSp8#t=29
Step 1:
http://stackoverflow.com/questions/1495812/c-how-to-add-a-zero-bits-byte-or-null-to-a-stringStep 2: "Also in C++, the std::string type can contain null characters just fine;"
