Ricardo Signes wrote:
> no strict;
> use 5.12.0;
> # strictures are still OFF here
>
> I think we're stuck with that, and that's all there is to it.
Should the same apply to feature.pm, too?
use feature "current_sub";
use 5.10.0;
# __SUB__ works here, because it was explicitly requested
So version declarations will simply set the default the strict.pm and
feature.pm will modify.
I do not mind having feature features added retroactively to existing
feature sets, but would you be willing to consider reintroducing
legacy.pm as an alternative? I think it simplifies things both in
terms of implementation and conceptually:
no legacy 'inc_operator';
On the other hand it might complicate things in future releases when
we cannot decide whether a new feature is actually the disabling
of a bug (e.g., feature "unicode_strings" is actually no legacy
"unicode_bug").
Thread Previous
|
Thread Next