I agree. I tend to solve this problem by having a namespace just for methods (sometimes one namespace just for class methods and another just for object methods). Then I write my code in an implementation namespace that is not searched for methods where I can write utility subroutines or import stuff with no worries. A simple demonstration might include:

package Cone::Head;
our $VERSION= '1.001_001';
use Cone::Head::code qw< new objectNamespace >;
package Cone::Head::Object;
use Cone::Head::code; # Imports all object methods (by default)
1;
[download]

package Cone::Head::code;
# ...
use Devel::NamedArguments qw< parseMethodArgs >;

sub objectNamespace {
    my( $we )= @_;
    return $we."::Object";
}

sub new {
    my( $we, %args )= parseMethodArgs(@_);
    my $me= init( \%args );
    return bless $me, $we->objectNamespace();
}

# $obj->init() will say: Can't locate object method "init" via package
+...
sub init {
   ...
}
...
[download]

The main drawback I find with this scheme is that caller is woefully inadequate at introspection. A more useful version of caller would be able to tell me that Cone::Head::Beldar->newFromDB() searched for newFromDB() for the class Cone::Head::Beldar and found newFromDB() in parent class Cone::Head where it had been imported from Class::NiftyORM where it was originally called CreateObjectFromDB() but the code inside that method actually considers its default package name to be Class::NiftyORM::code. A situation simulated by the following code:

package Class::NiftyORM::code;
sub Class::NiftyORM::CreateObjectFromDB { ... }

package Cone::Head;
*newFromDB= \&ClassNiftyORM::CreateObjectFromDB;

package Cone::Head::Beldar;
@ISA= qw< Cone::Head >;
[download]

So I'd like to be able to get the following information from something like caller:

• Subroutine (or method) names:
  • Original definition (appears after "sub" keyword), might be undefined
  • Called as (can also be undefined)
• Package names:
  • Default of compiled code (see prior 'package' statement)
  • Of original subroutine name (either above or appears after "sub" keyword)
  • Package (class) where sub was first searched for
  • Package (class) where sub was found (for non-method calls, same as above)

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.