Michael Rigby-Jones
> You are correct; they won't cause problems until you unknowingly define
> a symbol that the compiler uses (or the next compiler that someone may
> use).  Using the compilers namespace like this is bad practice, but and
> is often propagated by people who look through the compilers header
> files and copy the style, not knowing any better. I am guilty of this, a
> lot of the code I wrote many years ago has include guards that start
> with a leading underscore, which I remove if I have to make any
> revisions.
> 
> Unfortunately even if a publication has a respectable image, that
> doesn't stop them publishing the odd bit of incorrect or misleading
> information.
> 
> Since the format of the function name is not critical, you could simply
> append a single character to the start and totally avoid any potential
> issues.

What character would you recommend I use? 


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