Quest 3.02 parentheses bug - Axe Software Forums

  Axe Software Forums
  Quest Developer Forum
  Quest 3.02 parentheses bug

Author Topic:   Quest 3.02 parentheses bug

Mega posted 08-10-2001 21:31 GMT
This is really getting annoying. I've been coding and saving my game file in a text editor. When I open the file from QDK, it works fine. When I run it, it works fine. However, if I save the file from QDK, instead of from the text editor, and then run it, I get an error message saying it couldn't open. When I then read my log file to check it out, I see the following:
INIT: Quest 3.02
INIT: Opening file C:\PROGRA~1\QUEST2\FIRSTG~1.ASL on 10/8/2001 at 4:28:26 PM
FATAL ERROR: Expected ) in 'command <look #lookthing#> if is <#lookthing#;> then exec <look; normal> else if ( $instr(#lookthing# 1 ) then exec <look #lookthing#; normal> else exec <look at #lookthing#; normal>'
FATAL ERROR: Unable to open C:\PROGRA~1\QUEST2\FIRSTG~1.ASL
And on top of that, when I then open the ASL file itself in a text editor, it's CHANGED! Even if I just saved it from QDK without adding a thing to it, it's still changed! And that change has taken away one of the end-parentheses that had been there before, which causes the prog to not run!
For reference, I'll add 2 subsequent posts, one with the code before this happened, and one after it happened.
Alex posted 08-10-2001 21:56 GMT
Cheers for pointing this out, I'll take a look into it.
Computer Whizz posted 08-10-2001 23:16 GMT
No bug..... just an error somewhere (after you altered it probably!)
re-look at your first if statement and look for a missing ")" ..... it's just after "instr(" ..... found it? >>>> put it in!
And since QDK turns the code into it's OWN code, then write's it, it changing code is not entirely surprising to me! I think you might have typed a wrong letter, done something that QDK doesn't understand or something similar, and QDK just thought "Well.... I don't know what that is so out the window!!".
Oh, and it would have been easier if you'd have used the same topic/this topic to post your latter code in relation of this "bug" (with all the space's, ect...). Just thought...
Computer Whizz
Mega posted 09-10-2001 12:53 GMT
Yes, I know exactly where it is. The problem is, I DID put it in! When I open the code (which I typed in a text editor) in QDK, and run it, it works fine. But when I open it in QDK, save it in QDK, and THEN run it, it doesn't work. By saving it there, QDK did something to my code which took out the parenthesis, and then tells me that it can't run because it's missing a parenthesis! It created the problem in the first place, not me!
Computer Whizz posted 09-10-2001 16:21 GMT
GOD DAMN PARATHISIS-WHATEVER's!!
LOL ;)
Well, I'll try this out tonight (cut and paste job.) and if it doesn't work - then I'll post my comments.
I just wanted to rule out programmer error completely..... thanx for the info!
Computer Whizz
Mega posted 12-10-2001 22:20 GMT
Alex, I just thought you should know that this bug doesn't just apply to parentheses. Sometimes it divides a line of code, which is enclosed in <> brackets, into two lines, and then complains that the start-brace doesn't have an end-brace on the same line! There are probably other manifestations too, but these are the only ones I can think of
:-)

Author	Topic: Quest 3.02 parentheses bug
Mega	posted 08-10-2001 21:31 GMT This is really getting annoying. I've been coding and saving my game file in a text editor. When I open the file from QDK, it works fine. When I run it, it works fine. However, if I save the file from QDK, instead of from the text editor, and then run it, I get an error message saying it couldn't open. When I then read my log file to check it out, I see the following: INIT: Quest 3.02 INIT: Opening file C:\PROGRA~1\QUEST2\FIRSTG~1.ASL on 10/8/2001 at 4:28:26 PM FATAL ERROR: Expected ) in 'command <look #lookthing#> if is <#lookthing#;> then exec <look; normal> else if ( $instr(#lookthing# 1 ) then exec <look #lookthing#; normal> else exec <look at #lookthing#; normal>' FATAL ERROR: Unable to open C:\PROGRA~1\QUEST2\FIRSTG~1.ASL And on top of that, when I then open the ASL file itself in a text editor, it's CHANGED! Even if I just saved it from QDK without adding a thing to it, it's still changed! And that change has taken away one of the end-parentheses that had been there before, which causes the prog to not run! For reference, I'll add 2 subsequent posts, one with the code before this happened, and one after it happened.
Alex	posted 08-10-2001 21:56 GMT Cheers for pointing this out, I'll take a look into it.
Computer Whizz	posted 08-10-2001 23:16 GMT No bug..... just an error somewhere (after you altered it probably!) re-look at your first if statement and look for a missing ")" ..... it's just after "instr(" ..... found it? >>>> put it in! And since QDK turns the code into it's OWN code, then write's it, it changing code is not entirely surprising to me! I think you might have typed a wrong letter, done something that QDK doesn't understand or something similar, and QDK just thought "Well.... I don't know what that is so out the window!!". Oh, and it would have been easier if you'd have used the same topic/this topic to post your latter code in relation of this "bug" (with all the space's, ect...). Just thought... Computer Whizz
Mega	posted 09-10-2001 12:53 GMT Yes, I know exactly where it is. The problem is, I DID put it in! When I open the code (which I typed in a text editor) in QDK, and run it, it works fine. But when I open it in QDK, save it in QDK, and THEN run it, it doesn't work. By saving it there, QDK did something to my code which took out the parenthesis, and then tells me that it can't run because it's missing a parenthesis! It created the problem in the first place, not me!
Computer Whizz	posted 09-10-2001 16:21 GMT GOD DAMN PARATHISIS-WHATEVER's!! LOL ;) Well, I'll try this out tonight (cut and paste job.) and if it doesn't work - then I'll post my comments. I just wanted to rule out programmer error completely..... thanx for the info! Computer Whizz
Mega	posted 12-10-2001 22:20 GMT Alex, I just thought you should know that this bug doesn't just apply to parentheses. Sometimes it divides a line of code, which is enclosed in <> brackets, into two lines, and then complains that the start-brace doesn't have an end-brace on the same line! There are probably other manifestations too, but these are the only ones I can think of :-)