From 63314e4761ae30d47101a840d43fb1e92cf31e85 Mon Sep 17 00:00:00 2001 From: "Philippe Bruhat (BooK)" Date: Fri, 7 Nov 2025 18:17:47 +0100 Subject: [PATCH] fix the variable name in the doc for ${^MAX_NESTED_EVAL_BEGIN_BLOCKS} This seems to have existed since 741a5c7396a0ca90a22ea8d8e0761c70c14b0a77 (the initial commit), so it definitely looks like a typo that wasn't spotted before. --- pod/perlvar.pod | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pod/perlvar.pod b/pod/perlvar.pod index 3c564e45f5..f66c63f05e 100644 --- a/pod/perlvar.pod +++ b/pod/perlvar.pod @@ -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's executed inside of an C or C (possibly via C) are affected.