Skip to content

fix the variable name in the doc for ${^MAX_NESTED_EVAL_BEGIN_BLOCKS} #23904

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 7, 2025
+2 −2
Merged

fix the variable name in the doc for ${^MAX_NESTED_EVAL_BEGIN_BLOCKS} #23904

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions pod/perlvar.pod
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -643,8 +643,8 @@ fact the above code is equivalent to
BEGIN { $n+=2 }
BEGIN { $n+=1 }

which makes it obvious why a ${^MAX_EVAL_BEGIN_DEPTH} of 1 would not
block this code.
which makes it obvious why a ${^MAX_NESTED_EVAL_BEGIN_BLOCKS} of 1
would not block this code.

Only C<BEGIN>'s executed inside of an C<eval> or C<require> (possibly via
C<use>) are affected.
Expand Down
Loading