| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
section
I added this section to the latest perldelta, and Dave M pointed out
that it should become a standard section in the future, so I have added
it to the perldelta_template.pod
|
| |
|
| |
|
|
|
|
| |
And add an assert to be sure that we are correct.
|
|
|
|
|
| |
Having tests fail because vim created a ~ file for something is just
annoying.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Patch 8b6a017ccef7126ae5bcac137fa9a45de4f2c155 added some malformed
entries to Porting/Glossary. (The entries were missing a trailing
colon).
These malformed entries would produce a cryptic one-line warning,
but only when various files were being regenerated. To make things
more difficult these warnings would be produced at the top of, or
in the middle of a large stream of other compilation actions, easily
allowing one to overlook them. Even if you noticed them the information
provided did not make it particularly easy to figure out what was wrong.
This patch changes things so that the warnings contain more information,
it also causes configpm to die, and thus break the build process, once
it finishes scanning the glossary if there were any warnings during
processing. This allows us to avoid whackamole when dealing with multiple
broken entries, and makes it painfully obvious if there are issues
processing the glossary file, which should prevent any future repeat
of the errors in 8b6a017ccef7126.
|
|
|
|
|
|
|
|
|
| |
Patch 8b6a017ccef7126ae5bcac137fa9a45de4f2c155 added three
new entries to Porting/Glossary. These entries were malformed
from the point of view of configpm, which would warn about them.
This fixes the entries, by adding a missing colon to the first
line of each glossary entry.
|
|
|
|
| |
convention
|
|
|
|
|
|
| |
Which we use to document a mistake in perl5180delta.pod.
This patch also removes the mistake from perl5180delta.pod
|
| |
|
|
|
|
|
|
|
| |
isascii() is used as a fallback for isASCII(). This would be on an
unusual platform or under unusual circumstances. isascii() may return
values besides 0 and 1 which can cause things that are expecting a bool
to fail.
|
|
|
|
|
|
| |
The only time the result of toFOLD_LC() can be larger than a byte is
in a UTF-8 locale, which has already been ruled out for this section of
code.
|
|
|
|
|
|
| |
Commit 31f05a37 mistakenly included a line that is supposed to be in a
future commit. This reverts that until then; and adds a test for it, as
this was not caught by the test suite.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Currently this is only used during make test, and allows setting
the environment of the target before running tests.
|
| |
|
|
|
|
|
|
| |
This only required some minor changes to the Solaris hints, and
adding a few lines for Solaris in the part of Configure that handles
setting osname and osvers when cross-compiling.
|
| |
|
|
|
|
|
| |
Now, like with Android and plain Linux, cross-compiling to QNX (which
includes newer Blackberry devices) will load hints/qnx.sh.
|
|
|
|
|
|
|
|
|
|
| |
RXf_IS_ANCHORED as a replacement
The only requirement outside of the regex engine is to identify that there is
an anchor involved at all. So we move the 4 anchor flags to intflags and replace
it with a single aggregate flag RXf_IS_ANCHORED in extflags.
This frees up another 3 bits in extflags.
|
|
|
|
| |
So they stay stable as I move other flags from extflags to intflags
|
|
|
|
|
|
|
|
| |
This required removing the RXf_GPOS_CHECK mask as it uses one flag
that will stay in extflags for now (RXf_ANCH_GPOS), and one flag that
moves to intflags (RXf_GPOS_SEEN). This mask is strange however, as
you cant have RXf_ANCH_GPOS without having RXf_GPOS_SEEN so I dont
know why we test both. Further investigation required.
|
| |
|
|
|
|
|
| |
Includes some improvements to how we dump regexps so that when a regexp
is for the standard perl engine we also show the intflags for the engine
|
|
|
|
|
|
|
|
|
| |
[DELTA]
5.86 Thu Jan 30 08:24:28 MST 2014
- improved the performance of hexadecimal output functions
-- ref. 'shahex' in src/sha.c
-- thanks to Thomas Drugeon for ideas and test script
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
A patch has been submitted.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Brings:
sub { my $x; my $y; return 1; }
Up to speed with:
sub { my ($x, $y); return 1; }
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Commit 119ee68b changed the method to determine if a locale is a UTF-8
one to a method that was usable on more platforms, by using the C99 libc
function mbtowc(). I didn't realize that there needs to be a special
call to this function preceeding the main call to make sure it is in the
initial state. This commit fixes that.
In looking at the results from several different platforms, I decided it
is best to use nl_langinfo() in preference to mbtowc() when available,
and only use mbtowc() if nl_langinfo doesn't exist on the platform or
fails to return a real result, which happens for some locales on Darwin.
This commit does that as well.
|
|
|
|
| |
This adds a couple of lines of information, and sorts some other output
|
| |
|
|
|
|
|
|
|
| |
Commit 31f05a37 introduced a regression in which if you have something
like /[\s\d[:punct:]/, all but the final class were ignored. This was
due to initialization happening every time through the loop, instead of
the first time needed.
|
|
|
|
|
| |
Properly indent 9 lines. This makes it easier to see the logic flaws to
be fixed in the next commits.
|
|
|
|
|
|
|
|
|
|
|
| |
This code was recently moved from lib/locale.t to a new file essentially
unchanged, so that it could be common code. It deletes several
environment variables, such as PATH, to avoid interference with going
out and looking at the locales. In lib/locale.t, those environment
variables are not needed again, but that isn't true of all the callers.
The solution is simply to localize the removal.
This should fix [perl #121106], but there remain test failures there.
|
|
|
|
|
| |
exec's behavior is determined by the count of items in LIST, and
not by whether it's an array.
|
| |
|
|
|
|
|
|
|
| |
This was due to a logic error in toFOLD_LC() introduced in
31f05a37c4e9c37a7263491f2fc0237d836e1a80. It affected only the code
point at 0xB5 and shows up only in locales in which the character at that
code point is an uppercase letter.
|
|
|
|
| |
I somehow missed this.
|