I know that, in most cases, subroutines should not be named after built-in functions. Makes perfect sense to me. However, what about method names? 
my $newobj = My::Class->new();
$newobj->return();
$newobj->split();
$newobj->delete();

[download]
Is this also bad practice? I think the answer is, "Yes this is bad. Don't do it." But I would like a consensus, because I'm not as certain as I'd like to be. I may even reverse my opinion if given good reason.

The reason I ask is that I just noticed that vim was highlighting one of my method names different from all the rest. Turns out it was a Perl built-in name, also. Oops!

In reply to Built-in Function Homonyms for Method Names Bad, Too? by jffry

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.