On Fri, Mar 03, 2000 at 06:41:09PM -0600, Brad Appleton wrote:
> On Fri, Mar 03, 2000 at 07:01:29PM -0500, Michael G Schwern wrote:
> > The following is a minor correction so it reconizes both "\015" and
> > "\012\015" as empty, blank lines. I don't know if you want to adjust it
> > for the OS.
>
> Would it be more portable or easier to simply chomp the string (in
> a non-permanent/destructive fashion ;-) and check that against /^\s+$/
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.
I've made up my mind and I'll definately say that in this case perl
should want to handle all types of newlines transparently. I can't
think of any good reason why you'd legitimately want "\015\012" in a
POD document on a Unix machine unless you accidentally (or
purposefully in the case of perldos.pod and perlwin32.pod) got a POD
file with DOS newlines.
> > $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? :) It has nothing to do
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?
--
Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED]
Cheating is often more efficient.
- Seven of Nine
