I won't argue in favor or against exceptions, but your points contain some inaccuracies.
- die and croak can deliver objects to $@ quite fine. If you croak with an object, that object is passed to die and you can evaluate that object in $@ as you like. It loses the stacktrace, but then, you don't get a stacktrace by returning error integers/objects as well.
- The debugger has no problems with eval. You wouldn't know, of course, if you never used it, but then why raise the issue?
- Also, to clarify something you wrote in Re^4: Can someone please write a *working* JSON module: eval BLOCK does not "spawn a new interpreter".
If you don't like the keyword
eval, then you can have
try/catch as of Perl 5.34. There are also several CPAN modules offering that, and of course they're all
eval wrappers, because that's just the mechanism Perl always had. The point of the modules isn't about using different words, but avoiding the pitfalls with localized
$@ (The docs of
Try::Tiny give some details).