Beefy Boxes and Bandwidth Generously Provided by pair Networks
No such thing as a small change

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

I am in inner turmoil about my placement of use statements in modules, and I wonder if some kind monks have any opinions to share. The goal is some kind of conceptual purity, and I've tried a variety of approaches but I'm never happy with one for longer than a module or two. Should the statements come before or after the package statement? Organized alphabetically, or by importance, or by type (pragma, module, base module)?

Stuff I've tried:

  1. package statement, then alphabetical listing like:
    package Foobar; use constant STR => 'quack'; use Data::Dumper; use Quux; use strict; use warnings;

  2. package statement, pragmas, modules, base modules:
    package Foobar; use constant STR => 'quack'; use strict; use warnings; use Data::Dumper; use base 'Quux';

  3. "importance":
    package Foobar; use base 'Quux'; use constant STR => 'quack'; use strict; use warnings; use Data::Dumper;

  4. (My current thoughts) Order by non-package-specific pragmas/modules, package statement, package-specific pragmas/modules.
    use strict; use warnings; use Blarney; package Foobar; use constant STR => 'quack'; use Data::Dumper; use base 'Quux';

The last one I think is the most precise, with a distinction between stuff that needs to be imported into the package Foobar vs. stuff that can exist happily in package main. But it may also be more confusing to someone just looking at the code. {sigh} Thoughts? TIA, djantzen

"The dead do not recognize context" -- Kai, Lexx

In reply to Location of 'use' statements by djantzen

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, 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, 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.
  • Log In?

    What's my password?
    Create A New User
    [Corion]: Oh yay. The (external, not guided by me) programmers have chosen Moose+DBIx::Class for some implementation, and now seem to do 1+n SELECT statements for each row, as is usual when using ORMs.
    [Corion]: So maybe I should investigate how to plug in a cache in front of DBIx::Class so I can do a ->selectall_hashre f and then satisfy the "sub"-selects from that cached single SELECT statement ...

    How do I use this? | Other CB clients
    Other Users?
    Others surveying the Monastery: (6)
    As of 2017-09-25 10:54 GMT
    Find Nodes?
      Voting Booth?
      During the recent solar eclipse, I:

      Results (279 votes). Check out past polls.