| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
This was introduced by 9df874cdaa2f196cc11fbd7b82a85690c243eb9f
in changing the name of some static functions. I didn't realize at the
time that the function was defined in embed.fnc, as none of the others
are, and it was always called with the S_ prefix form. Nor did I notice
the compiler warnings.
It turns out that the base name of this function is the same as a public
function, so I've renamed it to have prefix 'S_my_'.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
eabab8bcc
488bc5795
fb0c7c3c4
3c47da3c2
eea89386b
1f7c3e7c6
7aa8cb0de
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
This single line addition generates a very confused diff listing for the
generated file.
|
| | |
|
| |
|
|
|
| |
This single line change generates very a confused diff listing for the
generated file, so is kept separate form the other \b{wb} commits.
|
| |
|
|
|
| |
A previous commit changed how \X is implemented, and now we don't need
these anymore.
|
| |
|
|
| |
Add indentation, as the previous commit added a switch{} around these.
|
| |
|
|
|
|
|
|
|
|
|
| |
A function implements seeing if the space between any two characters is
a grapheme cluster break. Afer I wrote this, I realized that an array
lookup might be a better implementation, but the deadline for v5.22 was
too close to change it. I did see that my gcc optimized it down to
an array lookup.
This makes the implementation of \X go from being complicated to
trivial.
|
| |
|
|
|
|
|
|
|
| |
This will enable the next commit to add \b{gcb}.
I separated this out from that commit because the diff output here is is
very confused, not accurately showing the underlying changes. Actually
two data structures are being added for every character set, and nothing
else changed.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This changes where the symbols are defined to a single file each. This
may save text space, depending on the compiler. The next commit will
cause this hdr to be included in more places, so it becomes more
important to do this.
At the same time this removes the guard for #ifndef PERL_IN_XSUB_RE.
The code now is executed regardless of that. This is simpler, and
previously there might have been the possibility of uninitialized memory
being read, should re_comp.o be executed before recomp.o.
|
| |
|
|
|
|
|
|
|
|
|
| |
This is a partial implementation of a full inversion map generation
capability, which is why some code is indented more than necessary --
in the future there will be things that use that. But this is
sufficient for 5.22.
This allows for the generation of tables to handle the Unicode line
breaking properties, like GCB and WB. Future commits will actually use
this capability.
|
| |
|
|
|
|
| |
The test file generated by mktables will soon contain other types of
breaks than \X. This prepares for that by making a more general
function that can be the bottom level for each
|
| |
|
|
|
| |
No use for the utf8_to_vtf7 function has appeared in the first
nine years of its existence so it's not earning its keep.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This normalizes function definitions and addresses the most
egregious of the Totally Forgot to Indent At All problems that are
rampant throughout this file.
For now I've punted on normalizing indents and tried to be
consistent with whatever local variant seems to be in use. There
are 2-, 3- (!), and 4-space indents, along with a liberal
sprinkling of tab characters, most (but not all) of which seem to
be intended to be equivalent to 8 spaces.
I considered normalizing indents with some like
astyle -c --style=linux vms.c
but that produces 8400+ changed lines, which doesn't seem worth it.
|
| | |
|
| |
|
|
| |
The RMG now has one more verbatim line longer than 79 columns
|
| |
|
|
| |
So don't hard-code it to undef as was done in 1be1b388c18674b89.
|
| |
|
|
|
|
| |
When the whole test is skipped, the END block that does a chdir
to $start throws a warning because $start is not defined. So
check for definedness.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
This eliminates a branch in the usual case, at the expense of an extra
one in the rarer case, which allows us to collapse some error condition
code. It sprinkles some UNLIKELYs.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
This aligns to a tab-stop, making it easier for me to type the next
commit
|
| |
|
|
|
|
| |
This is in part because "" is easier to read than '', but more
importantly a future commit will want to have double quotish context in
places, and this makes it easier for me to convert to that.
|
| |
|
|
|
|
|
|
|
| |
Prior to this commit, if you said
prop_value_aliases("Any", "foo")
it would return "foo". But there really aren't any synonyms for the
"Any" property values, so it should return undef instead.
|
| | |
|
| |
|
|
|
| |
NEXTFROM() modified the item count while testing it, so the next use
saw the count (of -1) as non-zero and ended up trying to write ~1 bytes.
|
| |
|
|
|
| |
The trie_words av may not exist if -Dr was not enabled at compile time,
so we must be more defensive for debug output at runtime.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
References to PERL_FOR_X2P probably have to stay in case any third-party
code is #defining it. Likewise, NO_PERL_TYPEDEFS in vms/vmsish.h has to
stay because it actually is used by App::a2p.
Cross/Makefile.SH.patch still needs regenerating since it contains
references to x2p in the top-level Makefile.SH which were removed by
e5a8a0fbd7.
A few other references to x2p/a2p/find2p/s2p still remain, which I am less
sure about removing, plus some others in documentation which should stay
anyway.
|
| |
|
|
|
|
|
|
|
|
| |
Apparently I missed this back in eed5d6a149b02. When spawning a
subprocess without waiting, the return value is the pid of that
process, but we need to let pp_system know we're doing that so it
doesn't manipulate the value as if it were an exit status.
One symptom was that t/test.pl's watchdog would sometimes report
that it had failed to start when in fact it had started just fine.
|
| |
|
|
|
|
|
|
|
|
| |
//n was implemented by avoiding the primary side-effects of compiling
a capture when the flag was turned on; however some secondary effects
still occurred later in the same function, by using the value of the
'paren' variable - even as far as causing coredumps.
Setting paren to ':' when NOCAPTURE is enabled makes the rest of the
function act just as if it had parsed (?:...) instead of (...).
|
| |
|
|
| |
It can be solarisstudio* as well
|
| |
|
|
|
| |
This outdents some code whose enclosing block was removed in the
previous commit
|
