Quote:
|
Originally Posted by pbhead
so.... are you saying that there is a problem somewhere else in my code(very likely) and the compiler desided to put the error message here?
|
Yes.
What probably happened is you introduced a syntax error, but you know how the compiler will sometimes highlight the line after an error? When it finally figures out you mistyped something? If your syntax error occurs right before an #include statement, it'll instead highlight the first line in that inoffensive include file (or one of the many nested system include files).
I've often seen it when someone accidentally hits the keyboard and unknowingly inserts a random character at the very top of one of their source files.