On 2010-03-01 18:15, Dave Tweed wrote:
> Bob Ammerman wrote:
>>> I know, but there is something funny going on.  I looked at it with
>>> 'xxd' and you have a CR/^M/0x0D with no LF/0x0A, and I will bet that's
>>> confusing the compiler.
>>
>> If that's what is confusing the compiler then the compiler is broken. CR and
>> LF are both defined as whitespace characters and any number of consecutive
>> whitespace characters is treated as equivalent to a single space.
>
> Well, yes, but the concept of "newline" is still significant, especially
> with //-style comments.
>
> In this case, the compiler is not recognizing a bare CR as a newline, and
> therefore, the first line of the function definition is being commented out.
>
> -- Dave Tweed


Another thing that I do not think have been mentioned here yet...

The *list file* from the compiler should tell what the actual
interpretation of the input file was. It should tell if what
looks like multiple lines was read as a single line by the
compiler, not ?

Jan-Erik.
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist