> Albrecht Schlosser wrote: > > Question: should there also be a rule to cut trailing spaces before > > each commit? > > This sounds dubious, and I'm trying to think where that might > be a problem, but I /think/ I've encountered situations where > trailing spaces might actually be relevant, such as an > escaped tab > or escaped space.
Yup... This is tricky for me, because (and for utterly pointless reasons) I'm obsessed with stripping all the trailing spaces, so I am very much in favour of encouraging that... > I think there are cases where the compiler and/or shell > interpreters > can complain about a trailing backslash in a comment, > e.g. something > like: > > #ifdef 0 > A MULTI-LINE COMMENT > _______________ > / \ <-- > / Some ascii art \ <-- > \ diagram / > \_______________/ > #endif OK - I see that is a problem... I always tend to "box" these things in, so I don't get this failure, E.g. #ifdef 0 A MULTI-LINE COMMENT ************************************** * _______________ * * / \ * * / Some ascii art \ * * \ diagram / * * \_______________/ * ************************************** #endif SELEX Galileo Ltd Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
