+- Forum (https://www.boriel.com/forum)
+-- Forum: Compilers and Computer Languages (https://www.boriel.com/forum/forumdisplay.php?fid=12)
+--- Forum: ZX Basic Compiler (https://www.boriel.com/forum/forumdisplay.php?fid=11)
+---- Forum: Bug Reports (https://www.boriel.com/forum/forumdisplay.php?fid=15)
+---- Thread: Incorrect Line numbers (*solved*) (/showthread.php?tid=175)
Incorrect Line numbers (*solved*) - britlion - 03-07-2010
I'm getting an error in the code "illegal character _ at line xxx"
And there isn't one in line xxx.
I suspect that this line number comes from the assembler, and it's a line number based on the code stripped of comments and white space perhaps?
I've noticed that it's sometimes hard to pin down the correct line number for errors before.
Re: Incorrect Line numbers - boriel - 03-07-2010
britlion Wrote:I'm getting an error in the code "illegal character _ at line xxx"Than paste the piece of code which produces the error, so I can try to reproduce it here.
And there isn't one in line xxx.
I suspect that this line number comes from the assembler, and it's a line number based on the code stripped of comments and white space perhaps?
I've noticed that it's sometimes hard to pin down the correct line number for errors before.
Re: Incorrect Line numbers - britlion - 03-07-2010
*facepalm*
You know how you feel pretty stupid later on, when you see the answer?
It was a line with a comment in it, and that comment DID have a _ in it.
What I'd done was miss off the asm command a few lines earlier, and it was freaking out because a semicolon doesn't start the comment unless you're in assembler mode. It passed over the semicolon, into the comment, reached the _ and thought "that's weird" and quit.
It was sort of right about the line number.... but in a slightly confusing way. (I was there wondering why a comment was an issue, and assumed it was off on line numbers).
I think it's #include that might lead the line numbers astray in the assembler part.
Call this solved
Re: Incorrect Line numbers (*solved*) - boriel - 03-07-2010
Ok, closed.
I've found 3 *NASTY* bugs on O3 optimizations. Hope to solve them this evening (2 of them already solved).
I think we must test the new release this week, and if no bugs founds, release the 1.2.5 Stable, so we can move on to 1.2.6 and add *new* features.
Re: Incorrect Line numbers (*solved*) - britlion - 03-07-2010
Did you manage to reproduce the stack bug with the earlier version of fourspriter I listed?
Re: Incorrect Line numbers (*solved*) - boriel - 03-07-2010
britlion Wrote:Did you manage to reproduce the stack bug with the earlier version of fourspriter I listed?Not sure. I mean: I'm working on O2-O3 bugs that might be related to this. In fact, the memcopy routine was also *BUGGED* (and fixed), so if your program uses memcopy, wait till this evening.
Re: Incorrect Line numbers (*solved*) - britlion - 03-07-2010
Got it.
Technically it does - it's still FourSpriter.
I posted the whole thing though (and I haven't been using Optimization yet)
Got friends arriving soon, so won't be around until tomorrow anyway.