Re: Location of 'use' statements (tye)

[tye]

package FooBar;

## Always used:
use strict;
use warnings;

## Other modules:
require Some::OO::Module;
use Some::Function::Module qw( Func1 Func2 );

## Setup of this module:
use base 'Quux';
use vars qw( $VERSION @EXPORT_OK );
$VERSION= 1.001;
@EXPORT_OK= qw( ... );

## Globals:
use vars qw( $Master );
$Master= ...;

use constant _IdNo => 0;
use constant _Name => 1;
use constant _Pos  => 2; # Gee, we need "use enum" (:

with a general tendency to put shorter items before longer items first.

                - tye

[Aristotle]

This is very close to what I do. I think of strict and warnings as part of an extended shebang line. Exporter is ugly so I avoid it wherever possible; though when I use it, I tend not to treat it and its globals specially. Finally, I reserve require solely for deferred loading of modules. So I arrive at a layout like this:

#!/usr/bin/perl
use strict;
use warnings;

package FooBar;

use Some::OO::Module ();
use Some::Function::Module qw( Func1 Func2 );

use base 'Quux';

use vars qw($VERSION);
$VERSION= 1.001;

use constant _IdNo => 0;
use constant _Name => 1;
use constant _Pos  => 2;

Makeshifts last the longest.

[Anonymous Monk]

This is pretty much what I do, with the following differences:

package Blah;
use strict;

=HEAD1 NAME 

...

=cut

BEGIN {
   # If I have one
  use XXX;   # as required here
}

# pragma level 'use's
use vars qw(...);

# Core modules
# CPAN  modules
# local modules
# globals and initializing assignments

# actual code at this point

I personally prefer the POD at the top, since it encourages me to write it first and update it first. Keeping it in front of my face as the first thing I see when the editor opens the file helps keep that positive guilty feeling of "you didn't update the POD, did you?" going, with the result that I actually do update it.