in reply to method aliases with goto(&NAME)

ask if anyone sees any drawback to this approach.

There are none except in the name -- goto -- kinda like "eval" -- scary for the scaredy

OTOH *oldname = *newname;

Replies are listed 'Best First'.
Re^2: method aliases with goto(&NAME)
by citromatik (Curate) on Sep 17, 2013 at 11:04 UTC
    OTOH *oldname = *newname;

    Yes, I also thought about something like that, but the goto version allows to include more code in the legacy method if needed:

    sub legacy_code { warn ("This method is deprecated, use current_method instead"); goto(&current_method); }