How did you write such fragile or broken code that it breaks in the face of different (but native) line endings despite Perl pretty much taking care of that for you automatically? :)
I could see having a problem on an old Mac if you included test data in files having non-old-Mac line endings (but perhaps Perls on old Macs handle that case better than I would expect based on the line-ending logic that I am aware of as I have not looked at the old-Mac-specific parts of Perl's source code). And I could see having minor problems when including data files having Windows line endings and then using them on Unix (if you don't always strip trailing whitespace from text lines, as is wise).
With your (subsequent) mention of Devel::Examine::Subs and finding test failures on Windows (for 10 versions back), the specific failure cases appeared to me to be types of failures that would be rather far downstream from the direct impact of different line endings, so I didn't continue spending time trying to figure out how the failures happen. Perhaps you could just describe that to us?
- tye
In reply to Re: CPAN module unit test issues: OS line endings (how?)
by tye
in thread CPAN module unit test issues: OS line endings
by stevieb
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |