2010-03-07, 04:54 PM
*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
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