Original post by abrken
You should AT LEAST test the return value from ExecuteString, I'm sure it gives asINVALID_CONFIGURATION witch means : "Hey man, I cannot compile your code since you have made something wrong with the library BEFORE compiling".
Hm, okay, guess that makes sense.. I was only checking the outstream as I thought all errors would be printed there, guess I'll be a lot more rigorous with return values in the future. Still, would it be possible to keep the engine in a usable state even after an error like that or at least also print a visible message when it happens? It did confuse me a lot until I finally figured out what was going wrong.