Here's the question I ask - why do private methods fail in Perl's implementation of them? It's because of the following situation:
package Foo;
sub new { bless {}, shift }
sub _method1 { print "Foo::_method\n"; }
sub method2 { my $self = shift; $self->_method1 }
package Foo::Bar;
@ISA = qw( Foo );
sub _method1 { print "Foo::Bar::_method\n"; }
package main;
my $foobar = Foo::Bar->new;
$foobar->method2;
The code is being called from within the Foo class, but method lookup finds the _method1() within the Foo::Bar class. *shrugs* I'm not sure where this leads, but that's the reason why. :-)
------
We are the carpenters and bricklayers of the Information Age.
Then there are Damian modules.... *sigh* ... that's not about being less-lazy -- that's about being on some really good drugs -- you know, there is no spoon. - flyingmoose
I shouldn't have to say this, but any code, unless otherwise stated, is untested
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|