On Tue, 2 Mar 2010, Russell McMahon wrote:

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

Actually I see this several times a year. It's one of the joys of 
maintaining systems that run on both unix and windoz. But it's normally an
imported header file that causes the problem not a cut and paste (I think 
the editors are trying to be too clever here).

The end-of-line problem had crossed my mind when Jason originally posted 
but after several responses from others it seemed that Jason wasn't 
interested in pursuing the problem so I also lost interest in trying to 
help.

The funniest similar problem I came across many years ago involved a 
makefile with a backslash at the end of a line (for continuation). For 
those that don't know, putting a backslash at the end of the line escapes 
the following end-of-line. After a lot of head scratching as to why the 
make file wasn't working as expected it was discovered that there was a 
space character after the backslash and before the end-of-line. You 
couldn't see the space so the line looked ok. Once the space was removed 
everything worked as expected.

Regards
Sergio Masci

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