Branch: refs/heads/blead
Home: https://github.com/Perl/perl5
Commit: c06746dce9294ecbcea2fe5971680a2eee46ed0a
https://github.com/Perl/perl5/commit/c06746dce9294ecbcea2fe5971680a2eee46ed0a
Author: Yves Orton <demer...@gmail.com>
Date: 2022-10-31 (Mon, 31 Oct 2022)
Changed paths:
M perly.act
M perly.h
M perly.tab
Log Message:
-----------
perly.* - update perly files with more recent bison
I want to modify perly with a comment. But that would leave us with
output files that are out of date in comparison with the input files.
My bison is later than the last used for perl, so running it
without my patch makes large changes. Therefore I have separated the
change into two pieces, the first just updates everything using my
more modern bison, the second runs bison again with the change I
actually made. This is the first of the pair, nothing changes here
except that which bison changed.
Commit: fa88efeacd5d994ceacc035be21adaff50aaac7f
https://github.com/Perl/perl5/commit/fa88efeacd5d994ceacc035be21adaff50aaac7f
Author: Yves Orton <demer...@gmail.com>
Date: 2022-10-31 (Mon, 31 Oct 2022)
Changed paths:
M perly.act
M perly.h
M perly.tab
M perly.y
Log Message:
-----------
perly.y - add a diag_listed_as for Unimplemented
In 1557e6c32831defe4b25a924a88baf5f5e7bcbdd we added a perldiag entry
for 'Unimplemented', which was good. But in theory the message should
have been picked up by the diagnostics tests when it was introduced.
However, this error message is not constructed in the normal way, and
the string was not identified as a message. This adds the appropriate
comment in the appropirate place so that the diagnostics test will
notice it should it change in the future. This necessitated a
make perly_regen.
Compare: https://github.com/Perl/perl5/compare/d91f67a32206...fa88efeacd5d
