I think the correct solution is to set the svn:eol-style property to "native" on all files and establish a coding standard that PHP_EOL be used in strings rather than "\n".
I will test this solution when I have time. Kris On May 20, 2009, at 14:49, naholyr <[email protected]> wrote: > > Bernhard++, developers MUST know with what linebreaks they work, as > what encoding they use. > Too much magic here could hide important flaws in the application. > I'd add that if someone for any reason works with a header-builder for > some protocol like FTP, SMTP, POP, etc... the standard linebreak is > "\r > \n", how will they test those kind of features ? > > If you add this behavior, please not default to it anyway ;) > > > On 16 mai, 18:03, Bernhard Schussek <[email protected]> wrote: >> Hi, >> >> I agree with Fabian when he says he does not want to alter lime to do >> it automatically. Otherwise this would lead to very strange >> behaviour, >> because a test like >> >> $t->is("Line 1\r\nLine 2", "Line 1\nLine 2"); >> >> may suddenly not fail anymore, even if the developer explicitely >> wants >> to test for that case. >> >> Does the problem only apply to Heredoc strings? If yes, I would >> rather >> avoid Heredoc strings and name that as a best practice instead of >> adding magic to lime. >> >> Bernhard > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" 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/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
