On 2010-03-01 23:18, Jason Hsu wrote:
> I compiled the suspect version of my program, uncommented the
> declaration of delay_1_msec,  and looked at the *.pre file.
>
> I found that the line "void delay_1_msec (void)" was missing.  The
> other function declaration lines (like the one for the delay_20_usec
> function) was unaffected.
>
> So the preprocessor apparently ignored the "void delay_1_msec (void)"
> line.  From other replies, it seems that the preprocessor interpreted
> this line as part of the previous line (which is a comment).
>
> The big question: When you create a new line in your C code, how do
> you make sure that the preprocessor recognizes it as a new line rather
> than part of the previous line?
>

Very few editors today would make it into anything else then
a true "newline". In particular if you create this new line in
the same enviroment as where the compile runs. I do not remember
the thread history, but wasn't the actual lines copied from
some other environment ?

So in short, this isn't a problem realy and you will probably not
see it again in many years, so don't bother...

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