You would need two (or more) perl executables.
The downloaded CPAN (or other source) scripts/modules that don't follow
the conventions would either have to be ported to the local environment.
Or they would need their own executable that doesn't follow the standard.
One or more groups will suffer.
<chaim>
>>>>> "PS" == Peter Scott <[EMAIL PROTECTED]> writes:
PS> At 10:59 AM 8/4/00 +0200, Johan Vromans wrote:
>> > What if the default strictness of vars was a compile-time option to
>> > be decided by the administrator of each site?
>>
>> Good grief, no! Perl should be perl, and not depend on site issues.
>> And, in anticipation: yes, there _is_ a difference between "you must
>> install module FooBar.pm 3.14 before you can use this" and "you need
>> to rebuild your perl".
PS> It would not be "you need to rebuild your perl", but "the administrator of
PS> this site does not allow unstrict programming by default."
PS> Letting sites set strictness by default is just a way of giving some
PS> control to the ones who want it, not denying it to the ones who don't.
PS> I would like to go further and allow sites the ability to make perls that
PS> *can't* disable certain strictnesses, although that may not be viable with
PS> the strictnesses we have right now. Perl doesn't outlaw fascism (witness
PS> closures-as-objects); it just requires it be optional.
PS> This is a (not *the*) key to the acceptance of Perl for large projects in
PS> large institutions. You don't have to work for one or like the way they go
PS> about things, but if we can give them something that doesn't hurt everyone
PS> else then it's a win. At least by the "Big House" philosophy.
PS> --
PS> Peter Scott
PS> Pacific Systems Design Technologies
--
Chaim Frenkel Nonlinear Knowledge, Inc.
[EMAIL PROTECTED] +1-718-236-0183
