Torque_no_dso_generation Bug

The implementation if the TORQUE_NO_DSO_GENERATION flag breaks some extremely useful Torsion as how it currently works Torque will never report a syntax error on compile(). Currently the code looks like this...

bool CodeBlock::compile(const char *codeFileName, StringTableEntry fileName, const char *inScript)
{
#if defined(TORQUE_NO_DSO_GENERATION)
   // There is probably a better way to do this.  
   return false;
#endif

That comment was absolutely right... this breaks the script compile() command which Torsion uses to check for script errors. The proper fix is to move this check before the DSO is written further down in the same function.

if(gSyntaxError)
   {
      consoleAllocReset();
      return false;
   }   

// MOVED HERE BEFORE THE DSO FILE IS WRITTEN!
#if defined(TORQUE_NO_DSO_GENERATION)
   return false;
#endif

   FileStream st;
   if(!ResourceManager->openFileForWrite(st, codeFileName)) 
      return false;
   st.write(U32(Con::DSOVersion));

This way the script is compiled and error and warnings are pushed out to the console log, but the DSO is not written. I really hope to see this in the new 4.2 release.