>
> So I think it's a worthwhile goal to get the VMS-specific bits *out*
> of the test suite, by making the Perl behave in as standard a fashion
> as practicable and useful on VMS. We can now argue the exact
> meaning of
> "practicable and useful", if anyone wants :-)
I completely agree with this goal. Isn't it very ambitious, though?
Doesn't this mean, among other things, we'll have to clean up the
answers to that list that Tom Christiansen posted the other day?
>
> And hopefully, when we see test errors, they'll be few and mean that
> something really needs to be fixed, not that J. Linux Hacker changed
> a test without suitably VMSifying it.
This would be wonderful. It should mean that perl programs which didn't
have explicit environmental dependencies ("use vmsish", for example) could
run unchanged on Unix (Linux if you prefer) or VMS.
The fullfillment of this goal would mean that almost all of the CPAN
riches would be available to VMS users. As it stands now, we often see
posted complaints about not getting some important module to work or
boasts that they _have_ been able to get some particularly valuable
module _to_ work under VMS.
Having said that, I do recall seeing occasional inquiries in
comp.lang.perl.misc and .moderated where people can't get a
particular module to work on their particular Unix flavor or
another and even much more typically Windows. So,
100% CPAN portability may be impractical. Many modules on
CPAN only get tested on the origianl authors system, after
all.
> --
> Chuck Lane [EMAIL PROTECTED]
>
-Jordan Henderson
[EMAIL PROTECTED]
