Syntax error in input - after Engine Initialized
by Vashner · in Torque Game Engine · 04/13/2002 (12:26 am) · 3 replies
I see this in red text (line2 of the example) in the console. Is this something I can ignore? Does not seem to be causing a problem.
Engine Initialized...
Syntax error in input ( This is in red text).
Randy...
Engine Initialized...
Syntax error in input ( This is in red text).
Randy...
#2
Randy...
04/13/2002 (9:11 am)
It's just a single red line of text. No error info is generated. Just curious if anyone has seen this before.Randy...
#3
This isn't mean to pick on you, but some constructive criticism and suggestions for all developers:
If you get an error message/string you don't understand, try searching the torque engine code for the string. In this case, it immediately comes up only once, in scan.cc.
Generally, searching the code (and scripts) will find the file the error is coming from. Or the few possible places if it's a really generic string.
The next thing to do is to put a breakpoint on that line, and see where/when it is actually being called.
In this case, I have no idea. That's the 'else' of 'if(fileName)', so the only thing it could be is likely an in-memory compilation -- not sure what that would be offhand, as I've never seen this before. You should be able to find it easily in the debugger.
And, for the rest of us, it'd behoove us to put in at least less generic, more specific error messages. Like this could be "Error scanning through script code -- no file, must be in-memory." Or, something like that. ;)
d
04/13/2002 (1:13 pm)
Hey Randy -This isn't mean to pick on you, but some constructive criticism and suggestions for all developers:
If you get an error message/string you don't understand, try searching the torque engine code for the string. In this case, it immediately comes up only once, in scan.cc.
Generally, searching the code (and scripts) will find the file the error is coming from. Or the few possible places if it's a really generic string.
The next thing to do is to put a breakpoint on that line, and see where/when it is actually being called.
In this case, I have no idea. That's the 'else' of 'if(fileName)', so the only thing it could be is likely an in-memory compilation -- not sure what that would be offhand, as I've never seen this before. You should be able to find it easily in the debugger.
And, for the rest of us, it'd behoove us to put in at least less generic, more specific error messages. Like this could be "Error scanning through script code -- no file, must be in-memory." Or, something like that. ;)
d
Torque 3D Owner Marco Meier
Slickware Games