You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@perl.apache.org by James G Smith <JG...@TAMU.Edu> on 2002/03/04 17:26:05 UTC
Re: [patch] require 5.6.1 in autogenerated .pm files
Geoffrey Young <ge...@modperlcookbook.org> wrote:
>Stas Bekman wrote:
>>
>> since we use 'our' in the autogenerated .pm files, requiring 5.6.1 is
>> probably a good idea:
>>
>
>[snip]
>
>> package $module;
>> +require 5.6.1;
>
>it probably doesn't matter, but isn't that format deprecated now? bleedperl reports
>
>v-string in use/require non-portable at -e line 1.
>
>for formats like that (with warnings enabled), so I've been changing all mine to
>
>require 5.006001;
>
>instead.
Well, `require 5.6.1' won't be understood by Perl before 5.6.0. I
don't think it's as much deprecated as not understood by the Perls
we're trying to avoid.
I don't see any problems with using it for other modules once we've
established we're in >=5.6.0.
Of course, if you really want a separater in there, you can always do
`require 5.006_001;'
That all said, `require 5.6.1;' will keep the code from running on
<5.6.1, but will give odd error messages for <5.6.0 (that is,
sensical error messages that don't point to the root cause).
That's my every-so-humble opinion. :)
--
James Smith <JG...@TAMU.Edu>, 979-862-3725
Texas A&M CIS Operating Systems Group, Unix
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: [patch] require 5.6.1 in autogenerated .pm files
Posted by Stas Bekman <st...@stason.org>.
James G Smith wrote:
> Geoffrey Young <ge...@modperlcookbook.org> wrote:
>
>>Stas Bekman wrote:
>>
>>>since we use 'our' in the autogenerated .pm files, requiring 5.6.1 is
>>>probably a good idea:
>>>
>>>
>>[snip]
>>
>>
>>> package $module;
>>>+require 5.6.1;
>>>
>>it probably doesn't matter, but isn't that format deprecated now? bleedperl reports
>>
>>v-string in use/require non-portable at -e line 1.
>>
>>for formats like that (with warnings enabled), so I've been changing all mine to
>>
>>require 5.006001;
>>
>>instead.
>>
>
> Well, `require 5.6.1' won't be understood by Perl before 5.6.0. I
> don't think it's as much deprecated as not understood by the Perls
> we're trying to avoid.
>
> I don't see any problems with using it for other modules once we've
> established we're in >=5.6.0.
I think it's been already established that mod_perl 2.0 requires 5.6.1,
5.6.0 is too buggy.
> Of course, if you really want a separater in there, you can always do
> `require 5.006_001;'
>
> That all said, `require 5.6.1;' will keep the code from running on
> <5.6.1, but will give odd error messages for <5.6.0 (that is,
> sensical error messages that don't point to the root cause).
So then I guess we should use 'require 5.006_001' everywhere. There are
just a few places where this is required.
_____________________________________________________________________
Stas Bekman JAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide http://perl.apache.org/guide
mailto:stas@stason.org http://ticketmaster.com http://apacheweek.com
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: [patch] require 5.6.1 in autogenerated .pm files
Posted by Geoffrey Young <ge...@modperlcookbook.org>.
>
> Well, `require 5.6.1' won't be understood by Perl before 5.6.0. I
> don't think it's as much deprecated as not understood by the Perls
> we're trying to avoid.
actually, I was intrigued by the "non-portable" ness of the warning - I thought it might mean that
5.6.1 wouldn't work on 5.6.1 on, say, windows or BeOS or some other platform 2.0 might be headed
toward. but I'm not really sure, though.
as I said, it probably doesn't matter :)
--Geoff
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org