It wouldn't be a problem if this is an application that will run for a long time and that you know it *will* use all this classes soon.

But if this is, for instance, a CGI application, you may want to switch to requires around your code to avoid the loading of classes you won't need in that run. This will reduce not only the memory use, but also the "boot" time.

The question of implementing plugins will not depend on the number of classes (as they might be doing completely different things), but on the number of classes doing the same type of things. Even then, it would depend if you switch on and off some of these classes to make sense (plugin means plug-in *and* plug-out).

daniel

In reply to Re: Are many use statements a code smell? by ruoso
in thread Are many use statements a code smell? by rlb3

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.