> \n = ox0a = unix > \r = 0x0d = macintosh > \r\n = dos OK, thanks. But when I read a file (using a python script, to see raw data), I have "\r\n". I'm under Linux. I should have "\n" then, right ? Maybe it's "vi" which deal with them.
I'd also expect svn to deal with these differences. What if some mac user commit a file with "\r", and a unix user like me open it ? Anyway... > So we now have 11 test (okay, some are very similar) * 3 boardfiles = > 33 examples. > Some of those won't compile (e.g. i2c_hardware on 16f88 or 16f648a), > but still quite a few new examples! Great ! I'll try to improve the script for automation. Particularly, I need to check if obtained samples are compilable ! Everything needed is in the script, it's just a matter of glueing the whole (as usual). Seb -- Sébastien LELONG http://www.sirloon.net http://sirbot.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/jallib?hl=en -~----------~----~----~----~------~----~------~--~---
