> > 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...

Let me translate that into Murphy-language, lest the lesson be lost :-) :

The problem was apparently caused by cutting and pasting between two
systems which dealt with the end of line condition differently.

This will very very likely never happen if a single system, or set of
consistently behaving systems* are used.

(*"A set of consistently behaving systems" is any set of systems in
which you have not yet found an inconsistency.**)

So you are quite likely to not see this again for a long while.

*SO* note very very very carefully what happened and why and how it
may apply in the most general terms to other similar and even not
similar actions, so that when it finally does happen again you have
enough memory of this event that the priosr knowledge process
invaluable.

Note that Murphy seems to know how long one's memory span is and what
the lesson was that we learned, and waits a suitable time before
providing a similar problem which we might otherwise solve too easily.



      Russell


** Similarlly: A bug free program is a program in which the latest bug
has not yet been noticed.
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist