> > Correct me if I'm wrong, but I believe it's not an issue of the line > number it is complaining about, but rather that it indicates the wrong > code is at fault? The actual error is that you're assigning a > function pointer to an integer, but with the ^M in comments, despite > stating the correct type of error, gcc indicates ".f = foo" is the > error instead of ".c = foo". > > I just tested with gcc 4.8.2, and this still seems to be the case. > Yeah, I am not familiar with gcc internals at all, but It seems like there's disagreement about the line numbering between the subsystem that parses/analyzes code and the one that displays the error messages. -- Andrey Smirnov Software Engineer Synapse Product Development mail 1511 6th Ave Suite 400, Seattle, WA 98101 office 206-381-0898 ext 4055 | mobile 253-254-6715 | fax 206-381-0899 andrey.smirnov@xxxxxxxxxxx | http://www.synapse.com
