| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
s/and/any/
perl -c documentation has a typo when talking about BEGIN blocks.
Steven Humphrey is now a Perl author.
For: RT #129313
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This bug was exposed by the tests that I'm still developing
|
|
|
|
|
|
| |
It was only testing matches against strings without a trailing
null byte. Now it also tests compilation of patterns without
a trailing null byte.
|
|
|
|
|
|
|
|
| |
The regex engine expects the pattern to have a null byte at
SvEND(pat), but is not guaranteed to receive such a pattern
when it is called, so S_concat_pat should guard against this
case. It turns out this is only an issue when there is exactly
one "argument" to the pattern. (Consider concatenation rules, etc).
|
|
|
|
|
| |
This expression dates back to about 2003 or so, and as
far as I can tell is no longer necessary.
|
| |
|
| |
|
|
|
|
| |
This was causing a failure in t/porting/podcheck.t.
|
| |
|
| |
|
| |
|
|
|
|
| |
I had already documented the perlinterp change.
|
|
|
|
|
|
|
| |
It is only needed for one block of tests. Leaving the handler in
place makes it harder to add temporary diagnostics elsewhere in
the code. (Where did my warning go? Hey, why is ‘warn’ not work-
ing?????!!!! :-)
|
|
|
|
|
|
|
|
| |
The & and &. operators were not appending a null byte to the string
in utf8 mode.
(The internal function that they use is the same. I used &. in the
test just because its intent is clearer.)
|
|
|
|
| |
Years out of date!
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
This is like the previous 2 commits, but the macro takes a flags
parameter so any combination of the disallowed flags may be used. The
others, along with the original isUTF8_CHAR(), are the most commonly
desired strictures, and use an implementation of a, hopefully, inlined
trie for speed. This is for generality and the major portion of its
implementation isn't inlined.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This macro follows Unicode Corrigendum #9 to allow non-character code
points. These are still discouraged but not completely forbidden.
It's best for code that isn't intended to operate on arbitrary other
code text to use the original definition, but code that does things,
such as source code control, should change to use this definition if it
wants to be Unicode-strict.
Perl can't adopt C9 wholesale, as it might create security holes in
existing applications that rely on Perl keeping non-chars out.
|
| |
|
| |
|
|
|
|
|
| |
This changes some formal parameters to be const, and avoids reusing the
same variable name within an inner block, to avoid confusion
|
| |
|
|
|
|
|
| |
This is a generalization of is_utf8_valid_partial_char to allow the
caller to automatically exclude things such as surrogates.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This changes the name of this helper function and adds a parameter and
functionality to allow it to exclude problematic classes of code
points, the same ones excludeable by utf8n_to_uvchar(), like surrogates
or non-character code points.
|
|
|
|
|
| |
These fill in gaps in current testing. In particular all the overlong
UTF-8 possible edge cases are now tested.
|
|
|
|
|
|
|
| |
This adds some information to test names, does some white-space
alignments, changes one test to stress things slightly more, and adds a
'use bytes' because in some cases the desired byte-oriented output was
not showing up.
|
| |
|
|
|
|
|
|
| |
I removed this in 35f8c9bd0ff4f298f8bc09ae9848a14a9667a95a, thinking the
warning was no longer being raised. But in fact, it was showing a bug,
now fixed by the previous commit.
|
|
|
|
|
|
|
|
|
|
| |
This combines EBCDIC and ASCII branches as much as possible, and fixes a
bug that showed up only on EBCDIC platforms, and 64-bit ASCII ones for
the highest overlong, where it could erroneously conclude that a
sequence was an overlong.
Tests are coming in a future commit.
.
|
| |
|
|
|
|
|
|
| |
Actually the code isn't quite duplicate, but should be because one
instance is wrong. This failure would only show up on EBCDIC platforms.
Tests are coming in a future commit.
|
|
|
|
|
| |
These correspond to strLT, etc. I am deferring documenting them in case
this turns out to be a bad idea for some reason.
|
|
|
|
|
|
|
|
| |
Prior to this commit, if there was a #define for memcmp that invoked a
version that Configure deemed to not be sufficient for normal use, it
was retained, so that perl used the defective version. This apparently
hasn't been a problem in the field, but I realized the potential issue
doing code reading, and am correcting it.
|