| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
These have always* had assignment precedence, such that
$a = goto $b = $c
is equivalent to
$a = (goto ($b = $c))
* I haven’t checked before perl 5.
|
| |
|
|
|
|
|
| |
Removed some out-of-date modules and add Math::GMPq, Math::GMPz and
Math:GMPf.
|
| |
|
| |
|
|
|
|
| |
There is no 'bitfloat' pragma
|
|
|
|
|
| |
Sometimes patterns with embedded code are recompiled each time even
if the pattern string hasn't changed.
|
|
|
|
|
|
| |
Update the docs and add perldelta entries summarising the changes and
fixes related to (?{}) and (??{}) accumulated over the 120 or so commits
in this branch.
|
|
|
|
| |
Not having such space has been deprecated since v5.14.0.
|
|
|
|
| |
(Thanks for reporting this, Tom Christiansen!)
|
|
|
|
|
|
|
| |
It was already documented that when scanning for the end of the string,
backslashes escaping the closing delimiter are being eliminated; but
this is true for backslashes escaping backslashes as well. This makes
that C<< '.\.' eq '.\\.' >>. (Pointed out by Mithaldu)
|
| |
|
| |
|
|
|
|
|
| |
This adds the parameter handling, tests, and documentation for this new
feature which allows locale and Unicode to play well with each other.
|
| |
|
|
|
|
|
| |
This has been superseded by c2f1e229, which adds it
to perlsyn.
|
|
|
|
|
| |
Here is a patch against the first patch,
fixing typos reported to me.
|
|
|
|
|
|
|
| |
The thrust of this patch is to move the description of the ~~
operator into perlop where it properly belongs; given and when
remain relegated to perlsyn. This is also (nearly) the first-ever
set of examples for the smartmatch operator. Staggerment.
|
| |
|
| |
|
|
|
|
| |
Signed-off-by: Abigail <abigail@abigail.be>
|
|
|
|
| |
This is to address ticket #94252.
|
|
|
|
|
|
|
| |
See the discussion starting with mail:9879.1315954489@chthon
This rephrasing should avoid people getting the impression // is a
source filter, translating 'A // B' into 'defined(A) ? A : B', and
reparsing the result.
|
|
|
|
|
| |
Make the indentation in this example match the surrounding
examples.
|
|
|
|
|
|
|
| |
The perlop manpage was stating ‘the left operand’, which was
not entirely correct, as ‘time.shift =>’ quotes just the shift,
not the time (nor does it see the whole as not being an ident-
ifier and refuse to quote anything).
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Subject: [perl #89490] PATCH: perlop.pod
|
| |
|
| |
|
|
|
|
|
|
| |
The reason there are links broken to this is that the X<>
were part of the heading, and the spaces between them are
significant
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This is apparently undocumented except in perldiag and a previous
perldelta.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I mostly fixed spelling mistakes, some of very long standing,
but a few files got more attentive word-smithying. I've updated:
pod/perl.pod
pod/perldelta.pod
pod/perl592delta.pod
pod/perl5120delta.pod
pod/perl51310delta.pod
pod/perl5139delta.pod
pod/perlfunc.pod
pod/perlop.pod
pod/perlrebackslash.pod
pod/perlrecharclass.pod
pod/perlutil.pod
pod/perlhack.pod
pod/perlintern.pod
pod/perlnetware.pod
pod/perlpolicy.pod
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Throughout 5.13 there was temporary code to deprecate and forbid
certain values of X following a \c in qq strings. This patch fixes
this to the final 5.14 semantics.
These are:
1) a utf8 non-ASCII character will croak. This is the same
behavior as pre-5.13, but it gives a correct error message, rather than
the malformed utf8 message previously.
2) \c{ and \cX where X is above ASCII will generate a deprecated
message. The intent is to remove these capabilities in 5.16. The
original agreement was to croak on above ASCII, but that does violate
our stability policy, so I'm deprecating it instead.
3) A non-deprecated warning is generated for all other \cX; this is the
same as throughout the 5.13 series.
I did not have the tuits to use \c{} as I had planned in 5.14, but \N{}
can be used instead.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Deprecate ?PATTERN?, recommending the equivalent m?PATTERN? syntax, in
order to eventually allow the question mark to be used in new operators
that would currently be ambiguous.
(With minor reconciliation edits by David Golden)
Signed-off-by: David Golden <dagolden@cpan.org>
|