I think this is generally a bad idea. Aliasing builtins may be fun, and may give you some builtins with names you like better, but it probably causes more trouble than it's worth. It makes it extrememly difficult for someone to maintain your code, for example. They're looking for Perl words and finding yours. In order to ensure they're properly understanding, they have to track back and forth through the code to find what your aliases are referring to.

If you prefer another language, use it. Then use a translator to convert your code into Perl, if that's what you want to do. You could even write your own translator to do this for you. But aliasing builtins is just asking for trouble, IMNSHO.

In reply to Re: Aliasing built-in Functions by spiritway
in thread Aliasing built-in Functions by codeacrobat

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.