Creating a secondary functional interface (like what CGI.pm does)
I don't like this at all. If you want to provide a secondary functional interface, please add a Foo::Bar::Functions or Foo::Bar::Simple module or some such instead. That way, the baggage doesn't have to be dragged around by everyone who probably doesn't even need it, nor adds extra mess in the main module to maintain. It also, and this I consider the greatest benefit, signficantly reduces the temptation to do dangerous and crufty things like trying to have one and the same subroutine handle both OO and non-OO calling conventions.

Makeshifts last the longest.

In reply to Re^2: Why should I use Exporter? (don't mix interfaces) by Aristotle
in thread Why should I use Exporter? by pernod

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.