develooper Front page | perl.perl5.porters | Postings from October 2011

Re: feature.pm proposal

Thread Previous | Thread Next
From:
Nicholas Clark
Date:
October 27, 2011 08:08
Subject:
Re: feature.pm proposal
Message ID:
20111027150836.GW23881@plum.flirble.org
On Mon, Oct 24, 2011 at 08:20:52AM +0200, Johan Vromans wrote:

> Instead of having 'use v5.14' do a 'no feature', rather have feature do
> an implicit 'all features off' before setting any feature bundle.
> 
> This would establish a clearly defined state no matter how we get there.

I agree.

Then I wondered, what should happen about "features" such as strict, or
the suggestion to 'use warnings' for v5.16. Currently we have:

$ ./perl -Ilib -le 'use v5.12; use v5.10; say $c'
Global symbol "$c" requires explicit package name at -e line 1.
Execution of -e aborted due to compilation errors.


Should that 'use v5.10' turn off strict, because that's part of "all
features off?". Hence should this?

$ ./perl -Ilib -le 'use strict; use v5.10; say $c'
Global symbol "$c" requires explicit package name at -e line 1.
Execution of -e aborted due to compilation errors.


Or are "strict" and "warnings" not features, but side effects, as they're
not defined as part of the feature module?

[I think the latter, but I'm not sure of a wording that doesn't make it look
like a special case]

Nicholas Clark

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About