| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
(cherry picked from commit 46f90daea602d22c11645273296e1e409a2640ea)
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
(manually cherry picked from commit 89a7d40e89d2f2e64fe5421cb28d5a1f29bb25b4)
[plus the maint-specific changes (%upstream and %bug_tracker) that weren't
pushed to blead to start with]
|
| |
|
|
|
|
| |
This is the same as it was in 5.22.0, but the book-keeping was missed.
|
| |
|
|
|
|
|
|
|
| |
(manually cherry picked from commit 133117f50ce47b68b460f4a9e0dd2ce37078d28c)
[Moved to th Incompatible Changes section, with som extra blurb by me
committer about the exception being made here.]
|
| |
|
|
|
|
| |
(manually cherry picked from commit f83db99040149dba7a484ba077bb60edb63bcb8c)
|
|
|
|
| |
(cherry picked from commit 8ca3d7d7d586051fc3f1f0a31ebec311138dfd8d)
|
|
|
|
| |
(cherry picked from commit 5ab3d1b305ca846b79acd114c0fe33773d1fcb5a)
|
|
|
|
|
|
| |
These were instituted commits prior to this one.
(cherry picked from commit 139a998acd6eae73587ff4f048925394f73682d9)
|
|
|
|
|
|
|
|
|
|
| |
The Unicode standard indicates that these breaks should succeed at the
beginning and end of text. It appears to me to be an oversight on their
part to not make an exception when there is no actual text. (Their test
suite does not cover this case.) I blindly implemented their algorithm
for 5.22, but it really is the wrong thing to do.
(cherry picked from commit a7a8bd1ed56dbdb7e63735924945bbb66b7e2e5c)
|
|
|
|
|
|
|
| |
Under \B{} the result is the complement of the \b{} result. However in
this code, the result was getting complemented again, wrongly.
(cherry picked from commit 67481c39e5c4241caaadaabb962ba281af64d9aa)
|
|
|
|
|
|
|
| |
The previous commit removed all but a single if statement each from
within the scope of other if statements. Combine them into one each.
(cherry picked from commit 00e3344b7aba855b0e0ace0c62580ed9dc74be15)
|
|
|
|
|
|
|
|
| |
These were thinkos. These things shouldn't have been in the
conditional, but after it so they are executed each time through the
loop.
(cherry picked from commit 43a7bd62098d36de61176a40d7eb3e72a2b9f033)
|
|
|
|
|
|
|
|
|
| |
The algorithm for determining a word break requires look-behind in some
cases. Certain characters are ignored in the look-behind, but until
this commit, the parse pointer was unchanged, causing things to get out
of sync in some edge cases.
(cherry picked from commit b4b2ec55cecba4503a6d679455fa72e5d81eda59)
|
|
|
|
|
|
|
| |
Some of these pass already, but may temporarily fail as a result of the
next few commits, until it all gets straightened out in the end.
(cherry picked from commit da271c5413343d25ab18d217cdc225c0be1633d9)
|
|
|
|
|
|
|
|
| |
This is fixed by not putting two adjacent '!' operators on the stack.
These are the only right-associative operators in the grammar, and they
just cancel each other out.
(cherry picked from commit a82f4918f5debccfb7e9a7047d2c2e558df538cd)
|
|
|
|
|
|
| |
See [perl #117341].
(cherry picked from commit a4395ebabc865511588235b5953dce6cc458ed3c)
|
|
|
|
|
|
|
| |
This adds /n to various places in perlre where it was omitted, and adds
a heading to better structure the document, and a clarifying sentence.
(cherry picked from commit 4cb6b3953a136d0cfac658452fec430c24730042)
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The issues seem to be much harder to trigger (harder than in VC6 or
Tru64, that is), though: the perl #125298 is the only spot where
the problem has surfaced so far. Though see also perl #126396,
with long doubles (the #125298 is with plain doubles).
All tests pass now in IRIX in blead with default config,
including the t/op/infnan.t. With -Duselongdouble nothing
new breaks (known issues with locales and M::BI)
(cherry picked from commit 6504068eb895d4fb6161ddbb0249e59c19afa707)
|
|
|
|
|
|
|
| |
Makes loc_tools users safe under minitest.
Currently op/quotemeta.t and op/taint.t are failing there.
(cherry picked from commit a274778c55a0011ece54485245cd8622d8f34570)
|
|
|
|
| |
(cherry picked from commit 9438e34a18209b9d8c49e08487ada02053c754dd)
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
[DELTA]
0.52 [2015-08-19]
- minimal Windows 10 support (thanks to Joel Maslak) [PR/8]
- refactor Windows 10 support to include ProductInfo flags
- add tests for Windows 8.1, 10, and 2012 R2 server
- define additional ProductInfo flags (TODO: add support for
these codes in _GetOSName)
(cherry picked from commit 083231ea891c049b70ef28512bfc9e68c3e5d595)
|
|
|
|
|
|
|
| |
This will make sure the GetVersionEx() is not going to lie to us
about the version of Windows we are running on.
(cherry picked from commit 9964c51f9e78a456ae7b7b5d79c43bd63a114f99)
|
|
|
|
|
|
|
|
| |
Commit 4fa6dd16d2149c2aeeb32633e3a796d5ebc5b657 added a message
when a quantifier was useless, but then caused the parse to skip it, so
that if it was in an illegal combination, that was no longer caught.
(cherry picked from commit d54288eb977c475e5eb044373c07e7873a1d90e7)
|
|
|
|
| |
(cherry picked from commit 5b9ce45660f01f87f17ed2211a1c01540d903a41)
|
|
|
|
|
|
|
|
| |
This was due to the '()' in the test case being empty, and not reducing
to an operand. The code didn't expect it, but was guarded by an
assertion. Now it generates a proper error.
(cherry picked from commit 174c9902b4705cef6307f83a226a0cb315b09ea7)
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If POSIX::strerror is passed $! as its arg, then it ends up doing
local $! = $!, which due to a bug in the localisation system, leaves $!
undef even after scope exit.
Work around the bug by assigning $_[0] to a my var first.
(cherry picked from commit 068e3fb46a24909060201961a41f2ab7fb778caf)
[POSIX.pm not $VERSION bumped, since it was already bumped by commit
ad5de5ac637094e4afcf8b206056a9202288aa76]
|
|
|
|
| |
(cherry picked from commit e011baf6f8ae4d213edb446fd811f9509b7abbb8)
|
|
|
|
|
|
|
|
|
|
| |
The \cX notation for control characters used to cause panics and unexpected
behavior when used insed an extended character class. See bug #126181.
The solution is to ignore the byte following \c during the first parsing
pass of a (?[]) construct.
(cherry picked from commit 4a84d6e89d52b8921090805085871e6cca66924d)
|
|
|
|
|
|
|
| |
Fixes a problem introduced by 57d2761b where ccflags contents
with quotes got broken by the quotes getting stripped.
(cherry picked from commit 7bd819935395fd684e09e3c97918ba0ad387288a)
|
| |
|
| |
|
|
|
|
|
| |
(Also leaving Incompatible Changes section for now since we expect to have
one: the fix for [perl #126319].)
|
|
|
|
| |
(manually cherry picked from commit f83db99040149dba7a484ba077bb60edb63bcb8c)
|
|
|
|
| |
(manually cherry-picked from commit 80e86009a1ba918b82ab94a400855d0168801db3)
|
|
|
|
| |
(cherry picked from commit 302ef3d4cab93d9ddf2bebde7e0952908332b8b2)
|
|
|
|
| |
(manually cherry-picked from commit 73d6481e251515b5d92adeb35d5a09b102f9304f)
|
| |
|
|
|
|
| |
(manually cherry picked from commit 0d610ac116dfe1f7752682b7e30e8019569d8adb)
|
|
|
|
| |
(cherry picked from commit ced634a413de975cd30ac5f5d08a1c43d2b402b3)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In IRIX longdouble (which uses the double-double format, bigendian)
multiplying with infinity introduces garbage bytes to the second double
of the double-double.
This garbage, in turn, seems to tickle another bug in long doubles,
in comparing infinities, where these garbage bytes errorneously matter
when they should not.
Workaround: zero these garbage bytes in multiplication.
The garbage bytes seem to appear only the multiplication, as far as
t/op/infnan.t can detect.
Even though we could place the multiplication result to a temporary NV
variable (for easier infiniteness inspection) for all the platforms and
depend on optimizer doing away with the temporary, let's be conservative.
(cherry picked from commit 3ec400f5ce53ea1a56d283bc6bf59e75762df058)
|
|
|
|
|
|
|
|
| |
Under some circumstances IRIX stdio fgetc() and fread() set the errno
to ENOENT, which makes no sense according to either IRIX or POSIX docs.
Just clear such an errno.
(cherry picked from commit bdae4172ce49ee233037d3e6af7dbeea521d0562)
|
| |
|