Branch: refs/heads/blead
Home: https://github.com/Perl/perl5
Commit: 087dc7fbe7f9871936ed58744a8c911ebb2ee5a3
https://github.com/Perl/perl5/commit/087dc7fbe7f9871936ed58744a8c911ebb2ee5a3
Author: Karl Williamson <[email protected]>
Date: 2025-10-17 (Fri, 17 Oct 2025)
Changed paths:
M toke.c
Log Message:
-----------
S_parse_ident: Add assertion
The source to parse must be in the buffer terminated at PL_bufend. This
was not obvious to me; this assertion would have caught my error
earlier.
Commit: aa93969e9c1841e58b08ecbe8d5df19488b49367
https://github.com/Perl/perl5/commit/aa93969e9c1841e58b08ecbe8d5df19488b49367
Author: Karl Williamson <[email protected]>
Date: 2025-10-17 (Fri, 17 Oct 2025)
Changed paths:
M embed.fnc
M embed.h
M proto.h
M toke.c
Log Message:
-----------
toke.c: Create function to see if an identifier is known
This checks first if there is a lexical variable in scope with the given
name, and if not, if there is a global
Commit: 3450d19250e29cc6fc0f4161db65d5995435c2ed
https://github.com/Perl/perl5/commit/3450d19250e29cc6fc0f4161db65d5995435c2ed
Author: Karl Williamson <[email protected]>
Date: 2025-10-17 (Fri, 17 Oct 2025)
Changed paths:
M embed.fnc
M embed.h
M proto.h
M toke.c
Log Message:
-----------
intuit_more: 'use strict' allows much better handling
Most code these days runs under 'use strict'. That allows us to resolve
ambiguity without resorting to heuristics in far more cases than before.
This commit adds a parameter to intuit_more() that gives the context it
is being called from. And when that call is to resolve what $foo[...]
is supposed to mean, we can look up foo to see if it is an array or a
scalar. If the former, the "..." must be a subscript; if a scalar, it
must be a charclass.
Only if there is both a $foo and an @foo is there ambiguity. If so, we
drop down to using the heuristics
Compare: https://github.com/Perl/perl5/compare/c2a46f9d3954...3450d19250e2
To unsubscribe from these emails, change your notification settings at
https://github.com/Perl/perl5/settings/notifications
