summaryrefslogtreecommitdiff
path: root/regen/feature.pl
Commit message (Collapse)AuthorAgeFilesLines
* Update docs wrt bitwise opsFather Chrysostomos2017-12-311-8/+4
|
* Enable bitwise feature with ‘use v5.28’Father Chrysostomos2017-12-311-1/+1
|
* revert smartmatch to 5.27.6 behaviourZefram2017-12-291-2/+2
| | | | | | | | | | | | | The pumpking has determined that the CPAN breakage caused by changing smartmatch [perl #132594] is too great for the smartmatch changes to stay in for 5.28. This reverts most of the merge in commit da4e040f42421764ef069371d77c008e6b801f45. All core behaviour and documentation is reverted. The removal of use of smartmatch from a couple of tests (that aren't testing smartmatch) remains. Customisation of a couple of CPAN modules to make them portable across smartmatch types remains. A small bugfix in scope.c also remains.
* update doc in lib/ about smartmatchZefram2017-11-221-2/+2
|
* RT #130907: Fix the Unicode Bug in split " "Aaron Crane2017-07-151-3/+4
|
* Bump feature.pm for 5.27.0Sawyer X2017-05-311-1/+3
|
* Revise documentation of eval and evalbytesKarl Williamson2017-02-191-45/+17
|
* Fix the Unicode Bug in the range operatorAaron Crane2017-01-051-2/+4
|
* Switch most open() calls to three-argument form.John Lightsey2016-12-231-1/+1
| | | | | | | | | | Switch from two-argument form. Filehandle cloning is still done with the two argument form for backward compatibility. Committer: Get all porting tests to pass. Increment some $VERSIONs. Run: ./perl -Ilib regen/mk_invlists.pl; ./perl -Ilib regen/regcharclass.pl For: RT #130122
* Patch unit tests to explicitly insert "." into @INC when needed.H.Merijn Brand2016-11-111-1/+1
| | | | | require calls now require ./ to be prepended to the file since . is no longer guaranteed to be in @INC.
* bump feature.pm $VERSIONDavid Mitchell2016-07-171-1/+1
|
* Update docs for declared_refsFather Chrysostomos2016-07-171-0/+16
|
* Add declared_refs feature featureFather Chrysostomos2016-07-171-0/+1
|
* Give feature.pm the concept of no-op featuresFather Chrysostomos2016-05-201-2/+9
|
* Remove @experimental from regen/feature.plFather Chrysostomos2016-05-201-7/+0
| | | | | | | | | | | Originally, we were going to have feature.pm warning when enabling an experimental feature. That changed, though, when we introduced the :all tag, because it is unkind for :all to warn. So in v5.17.6-49-g64fbf0d we started warning when a feature is used, not enabled. It does not appear that that will ever change, so we might as well remove the dead code (and comments) from regen/feature.pl.
* Increase $feature::VERSION to 1.44Father Chrysostomos2016-05-201-1/+1
|
* Update feature.pm docs for lex sub acceptanceFather Chrysostomos2016-05-201-8/+12
|
* feature.pm: add the v5.25 bundlev5.25.0Ricardo Signes2016-05-091-1/+3
|
* Make postfix dereferencing work without the postderef featureAaron Crane2015-07-131-12/+17
| | | | | The feature still exists, for compatibility with code that tries to enable it, but it has no effect. The postderef_qq feature still exists, however.
* Non-invasive mojibake fixesStanislaw Pusep2015-07-031-1/+1
| | | | | | Fixing minor encoding inconsistencies found by scan_mojibake utility (https://metacpan.org/pod/distribution/Test-Mojibake/bin/scan_mojibake) This patch is touching only comments/POD/__DATA__
* The postderef feature is no longer experimentalAaron Crane2015-06-271-10/+11
| | | | | | | | | | | | | | As proposed by RJBS. The "5.24" feature bundle (and therefore C<< use v5.24 >>) now enable postderef and postderef_qq. I can't find any precedent for what to do with the relevant experimental::* warnings category when an experimental feature graduates to acceptance. I have elected to leave the category in place, so that code doing C<< no warnings "experimental::postderef" >> will continue to work. This means that C<< use warnings "experimental::postderef" >> is also accepted, but has no effect.
* feature.pm remove unused lexicalsDaniel Dragan2015-06-031-2/+2
|
* feature: add the 5.23 bundle (same as 5.22)Ricardo Signes2015-06-011-1/+3
|
* feature.pm: Document the bitwise featureFather Chrysostomos2015-01-311-0/+18
|
* Increase $feature::VERSION to 1.40Father Chrysostomos2015-01-311-1/+1
|
* Add bitwise feature featureFather Chrysostomos2015-01-311-0/+1
|
* document the postderef feature in feature.pmRicardo Signes2014-11-221-1/+22
|
* Rename lvalue referencesFather Chrysostomos2014-10-171-3/+3
| | | | | Also correct the description of lvref magic. When it was first added, it was for list assignments only, but that soon changed.
* mention 'switch' is experimental in feature.pmDoug Bell2014-10-171-0/+6
| | | | The other experimental features already have nice warnings in feature.pm
* Document lvalue referencesFather Chrysostomos2014-10-111-0/+23
|
* Increase $feature::VERSION to 1.38Father Chrysostomos2014-10-101-1/+1
|
* Add lvalue_refs feature featureFather Chrysostomos2014-10-101-0/+1
|
* add a 5.21 feature bundleRicardo Signes2014-05-261-1/+3
|
* Change 'semantics' to 'rules'Karl Williamson2014-02-201-3/+3
| | | | | | The term 'semantics' in documentation when applied to character sets is changed to 'rules' as being a shorter less-jargony synonym in this case. This was discussed several releases ago, but I didn't get around to it.
* subroutine signaturesZefram2014-02-011-1/+22
| | | | | | | | | | Declarative syntax to unwrap argument list into lexical variables. "sub foo ($a,$b) {...}" checks number of arguments and puts the arguments into lexical variables. Signatures are not equivalent to the existing idiom of "sub foo { my($a,$b) = @_; ... }". Signatures are only available by enabling a non-default feature, and generate warnings about being experimental. The syntactic clash with prototypes is managed by disabling the short prototype syntax when signatures are enabled.
* Add postderef_qq feature featureFather Chrysostomos2013-10-051-0/+1
|
* Increase $feature::VERSION to 1.34Father Chrysostomos2013-10-051-1/+1
|
* Add postderef feature featureFather Chrysostomos2013-10-051-0/+1
|
* regen feature.pmRicardo Signes2013-05-181-1/+3
|
* Increase $feature::VERSION to 1.32Father Chrysostomos2012-11-241-1/+1
|
* Warn when declaring lexsubs, not when enabling themFather Chrysostomos2012-11-241-10/+6
| | | | | | | | feature.pm has an ":all" tag. So if we warn when lexical subs are enabled, then ‘use feature ":all"’ will also warn. That’s unkind. Instead, warn when a lexical sub is declared via ‘my/our/state sub...’.
* Increase $feature::VERSION to 1.31Father Chrysostomos2012-09-301-1/+1
|
* Use two colons for lexsub warningFather Chrysostomos2012-09-301-2/+2
|
* Document lexical subsFather Chrysostomos2012-09-151-0/+14
|
* Add experimental lexical_subs featureFather Chrysostomos2012-09-151-3/+25
|
* feature.pm: Missing spaceFather Chrysostomos2012-09-151-1/+1
|
* Increase $feature::VERSION to 1.30Father Chrysostomos2012-09-151-1/+1
|
* docs patch: 'unicode_strings' doesn't change utf8nessKarl Williamson2012-06-071-2/+3
| | | | | We had a field report of lack of clarity around this, so add some text.
* feature.pl: Make 5.even bundle imply 5.oddFather Chrysostomos2012-05-211-4/+6
| | | | | | Since the 5.18 feature bundle should be added long before 5.18, to avoid last-minute blunders, and since it’s easy to forget to do it in advance, have feature.pl do it automatically.
* add the 5.17 feature bundleRicardo Signes2012-05-201-1/+3
|
View Lorry Controller Status