| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
final expression value
|
|
|
|
| |
inside both try {} and catch {} blocks
|
|
|
|
| |
For: https://github.com/Perl/perl5/issues/18541
|
| |
|
|
|
|
|
|
|
|
|
| |
* Add feature, experimental warning, keyword
* Basic parsing
* Basic implementation as optree fragment
See also
https://github.com/Perl/perl5/issues/18504
|
|
|
| |
Originally missing the word "at", but rather than just adding it, this wording seemed nicer.
|
|
|
|
| |
For: https://github.com/Perl/perl5/issues/18260
|
| |
|
| |
|
|
|
|
|
|
|
| |
There used to be a section on Truth and Falsehood there, as the
following paragraphs talk about conditions and booleans a lot. It was
moved to perldata in 77fae4394e3ad9f159a74a6731a8d347cd2466c7, but
without a trace. Let's have a link to the new destination in the old one.
|
| |
|
|
|
|
|
|
| |
This paragraph can lead to ambiguity because it uses at example `for`
keyword but then says: Perl executes a foreach statement more rapidly
than it would the equivalent **for** loop.
|
|
|
|
|
|
|
|
|
| |
Alexandr Savca is now a Perl AUTHOR.
For: RT #133120
Committer: holding off on the corrections to pod/perlartistic.pod until
clarification of change to license text.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
| |
The operators affected by while-condition magic variously didn't mention
the implicit "defined" part of the magic or didn't mention it at all.
In perlsyn.pod there was a partial mention of the magic in the context
of the "for" loop, but none for the "while" loop. Describe the magic
more fully on both ends. [perl #132644]
|
|\ |
|
| |
| |
| |
| |
| | |
"whereis" is like "whereso" except that it performs an implicit
smartmatch.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
A "when" construct, upon reaching the end of its conditionally-executed
block, used to perform an implicit jump to the end of the enclosing
topicalizer, defined as either a "given" block or a "foreach" operating
on $_. Change it to jump to the enclosing loop of any kind (which now
includes "given" blocks).
|
| | |
|
| |
| |
| |
| | |
A "given" construct is now officially a one-iteration loop.
|
| | |
|
| |
| |
| |
| |
| |
| | |
Update documentation that describes old behaviour of given/when (of
various vintages) as current. Remove duplication. Edit the main section
in perlsyn for clarity. Properly document details of "break".
|
| |
| |
| |
| |
| |
| | |
Now that the biggest parts of the "Experimental Details on given and
when" are gone, merge the remaining part of the section into the "Switch
Statements" section.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Remove from "when" the implicit enreferencement of array/hash conditions
and the implicit smartmatch of most conditions. Delete most of the
documentation about behaviour of older versions of given/when, because
explaining the now-old "when" behaviour would be excessively cumbersome
and there's little compatibility to take advantage of. Delete the
documentation about differences of given/when from the Perl 6 feature,
because the differences are now even more extensive and it's too much
difference to sensibly explain. Add tests of "when" in isolation.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Change "given" from implicitly enreferencing array and hash topics to just
giving the topic scalar context. It's difficult to say whether this is a
change of the intended behaviour or merely a bugfix, because the implicit
enreferencement was not documented, and there were no tests exercising it.
The documentation merely said that the argument is in scalar context,
which correctly describes the new behaviour. Add a documentation note
about the old behaviour, alongside the existing notes about historical
given/when behaviour. Incidentally fix doc that referred to assiging
to $_, to instead refer to aliasing. Add tests for "given".
|
|/
|
|
| |
Fixes [perl #130958].
|
|
|
|
|
| |
This one-paragraph section didn't belong in perlsyn. perldata already
had a paragraph on the topic; merge them. [perl #115650]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Commit f5727a1c71878a34f6255eb1a506c0b21af7d36f tried to make yada-yada
be parsed consistently as a term expression, but actually things are
more complicated than that. The tokeniser didn't accept yada-yada in
the right contexts to make it usable as an expression, and changing
that would require decisions on resolving ambiguities between yada-yada
and flip-flop. It's also documented as being a statement rather than
an expression, though with some incorrect information about ambiguities.
Overall it looks more like the intent was for yada-yada to be a statement.
This commit makes it grammatically treated as such, and also fixes up
the dubious parts of the documentation. [perl #132150]
|
|
|
|
| |
For: RT #130324
|
|
|
|
| |
... and fix a typo.
|
|
|
|
|
|
| |
... also remove unused LOOP label from 'last' example, mention 'redo'
(works like 'next' in this case), add example that combines
'next'/'last' (and requires the label).
|
| |
|
|
|
|
| |
For: RT #123377
|
|
|
|
|
| |
Also correct the description of lvref magic. When it was first added,
it was for list assignments only, but that soon changed.
|
| |
|
|
|
|
|
| |
See thread beginning at
http://nntp.perl.org/group/perl.perl5.porters/219796
|
|
|
|
|
|
|
|
|
|
|
|
| |
Correct documentation which indicated that, inside a block, a semicolon after
an ellipsis statement would disambiguate between a block and a hash reference
constructor. The semicolon must precede the ellipsis to perform this
disambiguation.
Add tests to demonstrate that whitespace around the ellipsis statement does
not impeded the disambiguation. Add perldelta entry.
For: RT #122661
|
|
|
|
|
|
|
| |
An empty conditional in both for and while has been treated
as true since perl 1.0. This has a clear analogue in C/C++
in the case of for(;;), but while() is not legal C and should
be documented.
|
|
|
|
|
|
| |
The note explaining to use $c ~~ $_ instead of $_ ~~ $c was put under the item
introducing all binary operators, and not the one mentioning the explicit
smartmatch operator.
|
| |
|
|
|
|
| |
For: RT #118495
|
|
|
|
| |
[perl #118121]
|
| |
|
| |
|
|
|
|
| |
plus one typo fix
|
|
|
|
| |
(both reported by Tom Christiansen)
|
| |
|