Open tonycoz opened 2 years ago
Something else to consider here is the behaviour of no feature :some_bundle
, I'm not sure what I expect from that.
I feel this is unexpected behavior.
Is this fixed easily?
Are we think about the following ways?
use feature 'no_bareword_filehandles';
use feature 'no_multidimensional';
use feature 'no_indirect';
Something else to consider here is the behaviour of
no feature :some_bundle
, I'm not sure what I expect from that.
This isn't documented anywhere (only no feature 'specific_feature'
and no feature ':all'
are documented) so I don't expect anything in particular.
Something else to consider here is the behaviour of
no feature :some_bundle
, I'm not sure what I expect from that.This isn't documented anywhere (only
no feature 'specific_feature'
andno feature ':all'
are documented) so I don't expect anything in particular.
I mentioned it because of the final bit of code in https://github.com/Perl/perl5/issues/19271#issuecomment-992523695
Module: feature
Description
This may or may not be a bug, but i can see it being unexpected, but loading feature with a feature bundle that is missing some features does not disable those missing features.
This wasn't so confusing since for older bundles the extra features needed to be enabled explicitly (or via another bundle) anyway, but the 5.36 bundle disables some default enabled features, which may be confusing.
This isn't a problem for
use v5.35.6;
since that uses a different mechanism.If we do change this we may need to be careful with backward compatibility, possibly only making :5.36 and later remove the features not included in the bundle.
ping @rjbs since he removed "bareword_filehandles from :5.36" in d5c835da0b
Steps to Reproduce
(no error)
Expected behavior
Perl configuration