in reply to Re: Subclassing, done right?
in thread Subclassing, done right?

Currently, I am looking into Net::DAV::Server's new() function, which is where the executions seems to take the wrong path due to some variable being filled differently when working as a subclass..
Investigating...

Update: could extract an error, its in new()'s eval: "Undefined subroutine &Foo::_dav_child called at Foo.pm line 164" which is in my copy and pasted Foo.pm::propfind().
Why didn't use base import the _dav_child() function??

package Foo; use base Net::DAV::Server; sub propfind { # copy of the original propfind() from Net::DAV::Server # do something _dav_child(soemthing); }

Replies are listed 'Best First'.
Re^3: Subclassing, done right?
by Fletch (Bishop) on Aug 06, 2010 at 17:37 UTC

    I'm going to go out on a limb here (mind you it's a quite large, stout limb) and say "because it's an internal method not meant for export" (leading underscores are conventionally used for such subs).

    The cake is a lie.
    The cake is a lie.
    The cake is a lie.