In short, anyone else feel that the java/c way of 'overloading' subs based on the number of parameters is much cleaner then the perl way, and wish that you could use prototypes to do the same thing?
I certainly don't. It would be helpful if you could give an example of an application or a pattern where such a technique of distinct routines to handle different arglists would be useful.

Usually, a routine or method will do a particular job, and the bulk of the code will be independent of the form of parameter passing used. The rest of the code is a wrapper to handle the different types of parameters. This is polymorphism in action - what you are suggesting is violating one of the principles and advantages of OO. In Perl, rather than true polymorphism, most people adopt DWIM when designing the interface.

When it comes to perl's prototypes, I avoid using them, as they are nearly always more trouble than they are worth. I prefer the freeform arglist array that perl gives you in @_, and if I need something complicated, I cast (copy) it to a hash to implement named params.

Also, what I've just said applies to Perl 5. Perl 6 promises to provide much better ways of handling argument lists than Perl 5's prototypes.

In reply to Re: Prototypes allow overloading subs? by rinceWind
in thread Prototypes allow overloading subs? by BUU

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.