I'm doing some poop- What's a proper way to code method synonyms?

I've been doing:

# my imaginary method sub get_name { my $self = shift; $self->author or return; return "Your name is ".$self->author ". Hope you like it. "; } # my synonym sub name { my $self = shift; return $self->get_name; }

This get's tiresome/unmaintainable with 20+ methods.

What about with strictly procedural - that is.. subroutines.. should it be different? Where can I see some examples of this?
I didn't see much in super search under method synonyms

update

After reading the feedback on this original post- It appears to me that promiscuous use of method synonyms are a sugar cube with a drop of cyanide. Probably won't kill you, will taste like a sweet almond- and will likely make you sick.


In reply to what's a proper way to code method synonyms by leocharre

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.