Re: My AUTOLOAD doesn't work in newer Perls. How to fix?

goto &$name effectively removes the calling block from the call stack. With the eval block gone, how would you trap errors (it won't even return anything)? Pick one: have the eval block in the call stack (and then use &$f;), or don't try to trap errors.

Comment on Re: My AUTOLOAD doesn't work in newer Perls. How to fix? Select or Download Code

Replies are listed 'Best First'.
Re^2: My AUTOLOAD doesn't work in newer Perls. How to fix? by John M. Dlugosz (Monsignor) on May 17, 2011 at 09:46 UTC
I see what you mean. I don't expect it to trap an error in the dispatched function. I worry about an error in the `goto` itself, not finding the target or "going" there. Can that happen? I guess if $f is indeed not still undef and is a code ref, that should be good enough? Thanks.	[reply] [d/l]
Re^3: My AUTOLOAD doesn't work in newer Perls. How to fix? by JavaFan (Canon) on May 17, 2011 at 12:16 UTC
If you can live with just using `&$f` instead of `goto &$f`, then use that. (Just realize that `&$f` returns, while `goto &$f` doesn't - at least not to the place it was called from).	[reply] [d/l] [select]
Re^3: My AUTOLOAD doesn't work in newer Perls. How to fix? by moritz (Cardinal) on May 17, 2011 at 13:50 UTC
I guess if $f is indeed not still undef and is a code ref, that should be good enough? Yes. Perl 6 - second systems done right	[reply]
Re^3: My AUTOLOAD doesn't work in newer Perls. How to fix? by ikegami (Patriarch) on May 17, 2011 at 17:35 UTC
If `$f` is a code ref, you're good. Otherwise, `$f` is a symbol, and you can provide messages for `!exists(&$f)` and `!defined(&$f)`.	[reply] [d/l] [select]