I prefer having a variable too. I'd even do 

  our $Customer = My::Company::Namespace::Customer::; # <--- trailing 
+colons!

[download]
to make sure that I didn't mistype the class name. (See Re: Capitalized subroutine names and packages.)

Variables has the extra advantage of expanding right: 

  # Hi, this is written by me, the maintainer.
  do_something_with_class(Customer => \&callback);
  # Oops, I missed that Customer really was a
  # subroutine mimicing a bareword. *That* took a
  # while to figure out, huh!

[download]
Generally, I don't like to make stuff look like something it isn't.

ihb

See perltoc if you don't know which perldoc to read!
Read argumentation in its context!

In reply to Re^2: Module Naming Dilemma by ihb
in thread Module Naming Dilemma by Ovid

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.