Clear up ambiguous use of 'try block' #23955
Merged
+3
−3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Way back in 2001 several tests were added to t/op/goto.t which referred to a concept called a 'try block':
That language is still in use in two files -- but since we now have a 'try' keyword and a feature 'try', such language is now ambiguous.
Here we change 'try block' to 'eval block' in those test descriptions and comments where we're clearly speaking about 'eval BLOCK'.