Rik points out that we forgot to deëxperiment the "foreach list"
feature, which had been added in 5.36. Fair point.
On the PSC call today we reviewed the contents of perlexperiment.pod to
find a few more things that should be looked into.
A few seem easy:
:const attribute
foreach list
extra paired delimiters [*]
*: But please lets move the full list out of perlfeature.pod and into
some other doc!
One needs a bit of discussion:
try/catch -
I originally wanted to keep this experimental, partly for
considering how to add "typed catch" with filtering (as per
Syntax::Keyword::Try), and partly for thinking about how perl-core
exceptions might turn into real objects.
But it seems that maybe the first of those could just be a new
(experimental) feature on its own, and the second probably ought to
apply to eval+$@ as well, and have its own separate issues to think
about.
So maybe the basic try/catch form as it stands can be
deëxperimented after all...
Also some docs in perlexperiment.pod need fixing:
builtin has changed since the doc was written
feature 'class' needs adding
How do folks feel about declaring these stable (and hence removing the
experimental warnings) as part of 5.39.10, in time for 5.40?
*Technically* this falls outside of the stated change freeze, which is
worded as:
User-visible changes to correctly functioning programs
So, under a strict interpretation, maybe someone could argue that
removing an experimental warning does count as a user-visible change.
But on the other hand, if the program were warning of an experimental
feature, is it correctly-functioning? Does simply removing a warning
that has been suppressed by `no warnings ...` count as a user-visible
change?
Overall in PSC chat we felt that it would be nice to be able to ship a
5.40 where these features are declared stable, no longer printing
experimental warnings. In absence of any objections to the contrary
that's likely what we'll do.
How do people feel about this?
--
Paul "LeoNerd" Evans
leonerd@leonerd.org.uk | https://metacpan.org/author/PEVANS
http://www.leonerd.org.uk/ | https://www.tindie.com/stores/leonerd/
feature, which had been added in 5.36. Fair point.
On the PSC call today we reviewed the contents of perlexperiment.pod to
find a few more things that should be looked into.
A few seem easy:
:const attribute
foreach list
extra paired delimiters [*]
*: But please lets move the full list out of perlfeature.pod and into
some other doc!
One needs a bit of discussion:
try/catch -
I originally wanted to keep this experimental, partly for
considering how to add "typed catch" with filtering (as per
Syntax::Keyword::Try), and partly for thinking about how perl-core
exceptions might turn into real objects.
But it seems that maybe the first of those could just be a new
(experimental) feature on its own, and the second probably ought to
apply to eval+$@ as well, and have its own separate issues to think
about.
So maybe the basic try/catch form as it stands can be
deëxperimented after all...
Also some docs in perlexperiment.pod need fixing:
builtin has changed since the doc was written
feature 'class' needs adding
How do folks feel about declaring these stable (and hence removing the
experimental warnings) as part of 5.39.10, in time for 5.40?
*Technically* this falls outside of the stated change freeze, which is
worded as:
User-visible changes to correctly functioning programs
So, under a strict interpretation, maybe someone could argue that
removing an experimental warning does count as a user-visible change.
But on the other hand, if the program were warning of an experimental
feature, is it correctly-functioning? Does simply removing a warning
that has been suppressed by `no warnings ...` count as a user-visible
change?
Overall in PSC chat we felt that it would be nice to be able to ship a
5.40 where these features are declared stable, no longer printing
experimental warnings. In absence of any objections to the contrary
that's likely what we'll do.
How do people feel about this?
--
Paul "LeoNerd" Evans
leonerd@leonerd.org.uk | https://metacpan.org/author/PEVANS
http://www.leonerd.org.uk/ | https://www.tindie.com/stores/leonerd/