| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- linkify references to sections
- use EXTEND(SP, n) and PUSHs() instead of XPUSHs() where applicable
and update prose to match
- add POPu, POPul and POPpbytex to the "complete list of POP macros"
and clarify the documentation for some of the existing entries, and
a note about side-effects
- add API documentation for POPu and POPul
- use ERRSV more efficiently
- approaches to thread-safety storage of SVs.
- minor updates
|
|
|
|
|
|
|
|
|
| |
* Reformat code to make it more readable. The code should adhere to the
guidelines in the 'perlstyle' manpage. All changes are in the amount
of whitespace, e.g., all TAB characters are replaced by spaces. There
are no changes in the way the code runs.
* Increment version number to 0.40.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The following was produced for every non-miniperl object built,
including for XS modules and the test builds done by
ExtUtils::MakeMaker etc
..\iperlsys.h:640:66: warning: 'struct utimbuf' declared inside parameter list
typedef int (*LPLIOUtime)(struct IPerlLIO*, const char*, struct utimbuf*);
^
..\iperlsys.h:640:66: warning: its scope is only this definition or declaration,
which is probably not what you want
|
|
|
|
|
|
|
| |
A regex like /^a{5,}\z/ will match any string consisting exactly of 5 or
more "a" characters, but under debugging, the quantifier was previously
displayed as the numeric value of REG_INFTY (usually 32767). This commit
causes the upper bound to be displayed as "INFTY".
|
| |
|
|
|
|
| |
To correspond to stable CPAN release.
|
| |
|
| |
|
|
|
|
|
|
| |
If $x is a GV then *x's GP would be freed before $x's GP is assigned to
it. That would prematurely free $x, so protect it with a temporary ref
count bump.
|
| |
|
| |
|
|
|
|
|
| |
This will make sure the GetVersionEx() is not going to lie to us
about the version of Windows we are running on.
|
|
|
|
|
|
|
|
|
|
|
| |
[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)
|
| |
|
| |
|
|
|
|
| |
Though non-straddling, make the NV_MAX_EXP case identical.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
PERL_BUILD_EXPAND_CONFIG_VARS
Any person who built perl with this environment variable already has locked their
install to the given platform. Therefore this check should be unnecessary on
those installs. This reduces runtime bloat because Config does not have to be
loaded any time someone uses $! or Errno directly.
|
|
|
|
|
| |
The rest of the file automatically expanded Config variables, however the
module was still accidentally loaded. This commit corrects the oversight.
|
| |
|
|
|
|
|
|
|
|
| |
This may break places which have the FD_CLOEXEC functionality
but do not have the FD_CLOEXEC define.
In any case, using a boolean for the F_SETFD flag is icky.
Using an explicit 1 is also dubious.
|
|
|
|
|
| |
FD_CLOEXEC is currently usually the only defined fd flag
for F_GETFD/F_SETFD, but let's not assume that.
|
|
|
|
|
|
|
| |
Some of the test chose code points that did not match its assumptions as
to their classifications.
And some of the tests were extended to work on 1047 EBCDIC
|
|
|
|
|
|
| |
Whatever the bug was that caused some of these to need to be skipped,
it's gone now. Also some of the tests are easily adapted to work on
EBCDIC platforms.
|
| |
|
| |
|
|
|
|
|
|
|
| |
The tests for the Latin1 \xFF aren't a fair test of UTF-8 on EBCDIC
platforms, because it is generally a UTF-8 invariant character, so is
the same regardless of being in UTF-8 or not. This adds some tests
where the UTF-EBCDIC version is 2 bytes (as well as the UTF-8 version).
|
|
|
|
|
|
| |
This makes it easier to grep for these things. The typical test is for
the ord("A"), not some other character. Since this is in t/base, it
doesn't use helper scripts.
|
| |
|
| |
|
|
|
|
|
| |
These globals are already available; by using them instead of rolling
our own, it makes it easer to grep for these kinds of instances.
|
|
|
|
|
|
| |
This reverts commit 354f3e4ea74293dacec2ca84d3762435e9c45701.
This broken Win32 builds, see https://github.com/perl-pod/pod-simple/issues/69
|
|
|
|
| |
Spotted by Lukas Mai
|
| |
|
| |
|
|
|
|
|
| |
One message here uses a static array, and one uses a #define. I don't
think it really matters, but they should be adjacent.
|
|
|
|
|
|
|
|
|
|
|
| |
perl detects some locale errors when a new locale is entered. It stores
these up to output upon first use of something that uses that locale. A
synthetic start class (SSC) is used by the regex optimizer under certain
circumstances. Prior to this patch, it was possible for the stored up
bad locale message to not be raised if the match failed the SSC. This
patch fixes this by changing the node type of the SSC to be one that
checks for the stored-up message should there be locale-dependent
portions of the pattern.
|
|
|
|
|
| |
I was unaware of this construct when I wrote the commit that broke it,
and there were no tests for it. Now there are.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously use of this under /l regex rules was a compile time error.
Now it works like \b{wb} and \b{sb}, which compile under locale rules
and always work like Unicode says they should. A UTF-8 locale implies
Unicode rules, and the goal is for it to work seamlessly with the rest
of perl. This construct was the only one I am aware of that didn't work
seamlessly (not counting OS interfaces) under UTF-8 LC_CTYPE locales.
For all three of these constructs, use with a non-UTF-8 runtime locale
raises a warning, and Unicode rules are used anyway.
UTF-8 locale collation still has problems, but this is low priority to
fix, as it's a lot of work, and if one really cares, one should be using
Unicode::Collate.
|
|
|
|
| |
This will be used by the next commit
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The ANYOF_FLAGS bits are all used up, but a future commit wants one.
This commit frees up a bit by sharing two of the existing
comparatively-rarely-used ones. One bit is used only under /d matching
rules, while the other is used only when not under /d. Only the latter
bit is used in synthetic start classes. The previous commit introduced
an ANYOFD node type corresponding to /d. An SSC never is this type.
Thus, the bits have mutually exclusive meanings, and we can use the node
type to distinguish between the two meanings of the combined bit.
An alternative implementation would have been to use the
ANYOF_HAS_NONBITMAP_NON_UTF8_MATCHES non-/d bit instead of the one
chosen. But this is used more frequently, so the disambiguation would
have been exercised more frequently, slowing execution down ever so
slightly; more importantly, this one required fewer code changes, by a
slight amount.
|
|
|
|
|
| |
This is like an ANYOF node, but just for when /d is in effect. It will
be used in future commits
|
| |
|
| |
|
|
|
|
|
|
| |
Commit e128eaa17ab039e9db53073c7ac6c5093b3628d9 introduced 2 new overly
long verbatim pod lines that were causing podcheck.t failures in
pedantic mode. This suppresses those failures.
|