Branch: refs/heads/blead
Home: https://github.com/Perl/perl5
Commit: a7b8d88a7db0f93e2ec0bef63f0460d0d3247b10
https://github.com/Perl/perl5/commit/a7b8d88a7db0f93e2ec0bef63f0460d0d3247b10
Author: Karl Williamson <[email protected]>
Date: 2021-01-20 (Wed, 20 Jan 2021)
Changed paths:
M regcomp.c
Log Message:
-----------
regcomp.c: Change names of 2 macros for mnemonics
The new names are more understandable to me. This also adds a second
parameter to one macro, that is unused until the next commit in the
series.
Commit: e513125ac7bdea1f40ab055ab8c72da44de8f869
https://github.com/Perl/perl5/commit/e513125ac7bdea1f40ab055ab8c72da44de8f869
Author: Karl Williamson <[email protected]>
Date: 2021-01-20 (Wed, 20 Jan 2021)
Changed paths:
M embed.fnc
M embed.h
M proto.h
M regcomp.c
M toke.c
Log Message:
-----------
Revamp regcurly(), regpiece() use of it
This commit copies portions of new_regcurly(), which has been around
since 5.28, into plain regcurly(), as a baby step in preparation for
converting entirely to the new one. These functions are used for
parsing {m,n} quantifiers. Future commits will add capabilities not
available using the old version.
The commit adds an optional parameter, to return to the caller
information it gleans during parsing.
regpiece() is changed by this commit to use this information, instead of
itself reparsing the input. Part of the reason for this commit is that
changes are planned soon to what is legal syntax. With this commit in
place, those changes only have to be done once.
This commit also extracts into a function the calculation of the
quantifier bounds. This allows the logic for that to be done in one
place instead of two.
Commit: a25b770c008a6e530595a4b555443e2b65289a65
https://github.com/Perl/perl5/commit/a25b770c008a6e530595a4b555443e2b65289a65
Author: Karl Williamson <[email protected]>
Date: 2021-01-20 (Wed, 20 Jan 2021)
Changed paths:
M regcomp.c
M t/re/reg_mesg.t
Log Message:
-----------
Point to error in malformed /x{y,z}/
Prior to this comment a curly quantifier that had an error in the bounds
pointed to the left brace. Now the error message points to the first
bound that has a problem.
Commit: 20420ba9e016c0a7de5df27b5ab1fefd7902a766
https://github.com/Perl/perl5/commit/20420ba9e016c0a7de5df27b5ab1fefd7902a766
Author: Karl Williamson <[email protected]>
Date: 2021-01-20 (Wed, 20 Jan 2021)
Changed paths:
M embed.fnc
M embed.h
M pod/perldelta.pod
M pod/perlre.pod
M pod/perlrequick.pod
M pod/perlreref.pod
M pod/perlretut.pod
M proto.h
M regcomp.c
M t/re/re_tests
M t/re/reg_mesg.t
Log Message:
-----------
Allow empty lower bound in /{,n}/
This change has been planned for a long time, bringing Perl into parity
with similar languages, but it took many deprecation cycles to be able
to reach the point where it could safely go in.
This fixes GH #18264
Commit: b94d36b981ff593e5ccd66531069f12e0482b4f6
https://github.com/Perl/perl5/commit/b94d36b981ff593e5ccd66531069f12e0482b4f6
Author: Karl Williamson <[email protected]>
Date: 2021-01-20 (Wed, 20 Jan 2021)
Changed paths:
M toke.c
Log Message:
-----------
toke.c: Slight simplification
Rather than know how far we have advanced in parsing when we have to
back up, save the checkpoint position and simply backtrack to it. This
results in slightly more maintainable code that a future commit will
take advantage of.
Commit: c4e03e733b121b8cc35108564bddbb4a97d224d9
https://github.com/Perl/perl5/commit/c4e03e733b121b8cc35108564bddbb4a97d224d9
Author: Karl Williamson <[email protected]>
Date: 2021-01-20 (Wed, 20 Jan 2021)
Changed paths:
M toke.c
Log Message:
-----------
toke.c: Change variable name
A future commit will need it to represent just the meaning of the new
name
Commit: 6fab1cd3d01b1727683adef1fd9c531f4e7d4d62
https://github.com/Perl/perl5/commit/6fab1cd3d01b1727683adef1fd9c531f4e7d4d62
Author: Karl Williamson <[email protected]>
Date: 2021-01-20 (Wed, 20 Jan 2021)
Changed paths:
M toke.c
Log Message:
-----------
toke.c: White-space, comment only
Commit: fa2251a9e60c97eaa6070019b9da01efb26262dd
https://github.com/Perl/perl5/commit/fa2251a9e60c97eaa6070019b9da01efb26262dd
Author: Karl Williamson <[email protected]>
Date: 2021-01-20 (Wed, 20 Jan 2021)
Changed paths:
M dquote.c
Log Message:
-----------
dquote.c: Change variable name
A future commit will need it to represent just the meaning of the new
name
Commit: b8df2602b04f250c4d5467c4f180b89c1d0fcd72
https://github.com/Perl/perl5/commit/b8df2602b04f250c4d5467c4f180b89c1d0fcd72
Author: Karl Williamson <[email protected]>
Date: 2021-01-20 (Wed, 20 Jan 2021)
Changed paths:
M t/re/reg_mesg.t
Log Message:
-----------
t/re/reg_mesg.t: Add two missing test cases
I noticed in code reading that these error cases weren't tested for.
Commit: e8ba086966639eb1fc2185bfc1b5026ad30cfdd7
https://github.com/Perl/perl5/commit/e8ba086966639eb1fc2185bfc1b5026ad30cfdd7
Author: Karl Williamson <[email protected]>
Date: 2021-01-20 (Wed, 20 Jan 2021)
Changed paths:
M regcomp.c
Log Message:
-----------
regcomp.c: Slight simplification
Rather than know how far we have advanced in parsing when we have to
back up, use the already-existing checkpoint position. This results in
slightly more maintainable code that a future commit will take advantage
of.
Commit: 80318d2b040211edc9d94d10bc5d79497be66324
https://github.com/Perl/perl5/commit/80318d2b040211edc9d94d10bc5d79497be66324
Author: Karl Williamson <[email protected]>
Date: 2021-01-20 (Wed, 20 Jan 2021)
Changed paths:
M regcomp.c
Log Message:
-----------
regcomp.c: Move initialization into declaration
This is considered better practice.
Commit: abd9c16d55498b521a7dc3e5ae419ed149782f0a
https://github.com/Perl/perl5/commit/abd9c16d55498b521a7dc3e5ae419ed149782f0a
Author: Karl Williamson <[email protected]>
Date: 2021-01-20 (Wed, 20 Jan 2021)
Changed paths:
M regcomp.c
Log Message:
-----------
regcomp.c: Refactor portions of \g parsing
This moves the finding of the matching '}' for \g{ to earlier, and
creates a temporary to point to the current position in the parse. This
makes it easier to deal with backtracking; we haven't advanced the main
parse pointer, so don't have to remember how far we advanced. This will
prove advantageous in a future commit.
Commit: 12abe3c415ac316306426490edddd357e2cac4d3
https://github.com/Perl/perl5/commit/12abe3c415ac316306426490edddd357e2cac4d3
Author: Karl Williamson <[email protected]>
Date: 2021-01-20 (Wed, 20 Jan 2021)
Changed paths:
M regcomp.c
Log Message:
-----------
regcomp.c: Further refactor \g
By changing a bool into a pointer, we can avoid some work and prepare
for a future commit.
Commit: a44b2be795f4c5f94384c6f6010860588e144b3c
https://github.com/Perl/perl5/commit/a44b2be795f4c5f94384c6f6010860588e144b3c
Author: Karl Williamson <[email protected]>
Date: 2021-01-20 (Wed, 20 Jan 2021)
Changed paths:
M pod/perlre.pod
M regcomp.c
Log Message:
-----------
perlre: Note the other forms of \k<name>
Not all three synonyms were documented.
This also fixes up related comments in regcomp.c to correspond
Commit: 1b2f32d508340483aa270e0caf653ba0454345d1
https://github.com/Perl/perl5/commit/1b2f32d508340483aa270e0caf653ba0454345d1
Author: Karl Williamson <[email protected]>
Date: 2021-01-20 (Wed, 20 Jan 2021)
Changed paths:
M dquote.c
M embed.fnc
M pod/perldelta.pod
M pod/perldiag.pod
M pod/perlop.pod
M pod/perlre.pod
M pod/perlrebackslash.pod
M pod/perlrequick.pod
M pod/perlretut.pod
M proto.h
M regcomp.c
M t/opbasic/qq.t
M t/re/pat_advanced.t
M t/re/re_tests
M t/re/reg_mesg.t
M toke.c
Log Message:
-----------
Allow blanks within and adjacent to {...} constructs
This was the consensus in
http://nntp.perl.org/group/perl.perl5.porters/258489
Commit: 8e8b1eab53331e23b80288f2b237a391490bdbe1
https://github.com/Perl/perl5/commit/8e8b1eab53331e23b80288f2b237a391490bdbe1
Author: Karl Williamson <[email protected]>
Date: 2021-01-20 (Wed, 20 Jan 2021)
Changed paths:
M regcomp.c
Log Message:
-----------
regcomp.c: White-space and comments
Compare: https://github.com/Perl/perl5/compare/012ac233b0f8...8e8b1eab5333
