On Fri, Mar 03, 2000 at 08:42:27PM -0500, Michael G Schwern wrote:
> No, chomping would be platform specific (by $/). chomping "\015\012"
> on Unix will leave you with "\012" which will be considered to be
> 'non-empty' and the same spew of warnings will occur on perldos.pod
> and perlwin32.pod as happens now.
Then maybe I should just look for tabs and spaces a la /^[ \t]+$/ and
let all other newline-ish things go.
> > > $file = VMS::Filespec::unixify($file) if $^O eq 'VMS';
> >
> > Hmmn - I haven't seen that before. Is that needed for the DOS newline
> > thing or for some other reason?
>
> Dunno, I didn't add it. (What? You don't know /every/ line of code
> in your module like the back of your hand? :)
Actually - that line of code isn't in my master-copy of the module. I
know there are some minor differences between my copy and whats in the
core because the version on CPAN tries to work with 5.004 or later.
> with the DOS newline thing, it appears to be just for the formatting
> on the waring... but why would you want to format VMS filenames as
> Unix if you're on VMS?
It might have to do with getting consistent looking output that gives
reproducible expected results that look the same for both Unix and VMS
so that the t/pod/*.t tests pass when comparing output produced on Unix
vs VMS when the output contains input filenames.
--
Brad Appleton <[EMAIL PROTECTED]> http://www.enteract.com/~bradapp/
"And miles to go before I sleep." -- Robert Frost
