Parse errors in Starting Guide project
by Bram Custers · in Torque 2D Beginner · 01/31/2015 (10:04 am) · 3 replies
Hey guys,
I'm new to Torque and was just checking out the starting guide. Now, when I try to run the project, I get all sorts of weird parse errors, according to the console:
>>> Some error context, with ## on sides of error halt:
���»���¿if(!isObject(GuiDefautProfile)) new GuiControlProfile(GuiDefaultProfile);##
>>> Error report complete.
Executed D:/Gameprogramming/Torque2DProjects/TestProject/modules/MyModule/gui/guiProfiles.cs. Took 0 ms
D:/Gameprogramming/Torque2DProjects/TestProject/modules/MyModule/scripts/scenewindow.cs Line: 1 - parse error
>>> Advanced script error report. Line 1.
>>> Some error context, with ## on sides of error halt:
���»���¿function createSceneWindow(){
## ##
if( !isObject(mySceneWindow)){
//Create the scene window
...
//Place scenewindow on the canvas
>>> Error report complete.
I wrote the files in VS2013, and afterwards edited some in Notepad++ (thought it might have been encoding stuff...). Yet, still these parse errors keep popping up. Do you have any experience with these errors?
I'm new to Torque and was just checking out the starting guide. Now, when I try to run the project, I get all sorts of weird parse errors, according to the console:
>>> Some error context, with ## on sides of error halt:
���»���¿if(!isObject(GuiDefautProfile)) new GuiControlProfile(GuiDefaultProfile);##
>>> Error report complete.
Executed D:/Gameprogramming/Torque2DProjects/TestProject/modules/MyModule/gui/guiProfiles.cs. Took 0 ms
D:/Gameprogramming/Torque2DProjects/TestProject/modules/MyModule/scripts/scenewindow.cs Line: 1 - parse error
>>> Advanced script error report. Line 1.
>>> Some error context, with ## on sides of error halt:
���»���¿function createSceneWindow(){
## ##
if( !isObject(mySceneWindow)){
//Create the scene window
...
//Place scenewindow on the canvas
>>> Error report complete.
I wrote the files in VS2013, and afterwards edited some in Notepad++ (thought it might have been encoding stuff...). Yet, still these parse errors keep popping up. Do you have any experience with these errors?
#2
01/31/2015 (4:50 pm)
The dreaded missing semicolon - at least it was a small file. I was about 12k lines deep and missed one. Took me a couple of hours to track that down.
#3
01/31/2015 (9:23 pm)
That must've been quite a search I reckon ;) I read that the parser can act pretty weird when it comes to semicolons (linenumbers and such), so I guess I was lucky this time. 
Bram Custers