now torquescript will print out a more modern error message with a pointer to the offending character.
Multi line error outputs to be added to this for context
If the statement is a terminating statement on slot assignment (such as %var[%i]++;), the stack has to be popped everytime slot arrays are used regardless of the expression type.
unlike in the straight compile it now case it does in fact need to stick around. read injects the CodeBlock into a management system, so no worries about cleanup
Con::EvalResult CodeBlock::exec -
objectCreationStackIndex needs to be signed as we test if it goes sub-zero
ConsoleValue Namespace::Entry::execute -
compiler yells about returning a temp via std::move
bool TorqueScriptRuntime::executeFile -
report the name of the dso output file, not the source scxript input file
