Skip to content

Conversation

@book
Copy link
Contributor

@book book commented Nov 7, 2025

This seems to have existed since 741a5c7 (the initial commit), so it definitely looks like a typo that wasn't spotted before.

  • This set of changes does not require a perldelta entry.

This seems to have existed since 741a5c7
(the initial commit), so it definitely looks like a typo that wasn't
spotted before.
Copy link
Contributor

@jkeenan jkeenan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed.

$ grep -n -E '\{\^MAX_(EVAL_BEGIN_DEPTH|NESTED_EVAL_BEGIN_BLOCKS)}' ./pod/perlvar.pod 
604:=item ${^MAX_NESTED_EVAL_BEGIN_BLOCKS}
646:which makes it obvious why a ${^MAX_EVAL_BEGIN_DEPTH} of 1 would not

$ ack -l '\{\^MAX_NESTED_EVAL_BEGIN_BLOCKS}' .
INSTALL
pod/perl5380delta.pod
pod/perldiag.pod
pod/perlfunc.pod
pod/perltoc.pod
pod/perlvar.pod
t/op/eval.t
perl.h
op.c

$ ack -l '\{\^MAX_EVAL_BEGIN_DEPTH}' .
pod/perlvar.pod

@book book merged commit 63314e4 into Perl:blead Nov 7, 2025
34 checks passed
@book book deleted the book/fix-typo-in-the-doc-for-MAX_NESTED_EVAL_BEGIN_BLOCKS branch November 7, 2025 23:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants