in reply to Re^5: OOP: ->Coderef for calling Private Methods (possibilites?)
in thread OOP: Obj->Coderef for calling Private Methods

Yes THIS could be better. it says:
How does Perl know which package the subroutine is in? By 
looking at the left side of the arrow, which must be either
a package name or a reference to an object, i.e. something 
that has been blessed to a package. Either way, that's the 
package where Perl starts looking. If that package has no 
subroutine with that name, Perl starts looking for it in 
any base classes of that package, and so on.
...

The right side of the arrow typically is the method name, 
but a simple scalar variable containing either the method 
name or a subroutine reference can also be used.

If there was any paragraph saying something like

$obj->$coderef(@paras) is equivalent to $coderef->($obj,@paras) "no matter if the RHS and the LHS have any package relation"!
would be a much clearer definiton and avoiding the need to experiment. (well I'm not sure how to express the "no matter" part in clear English, but I hope the point is clear)

Cheers Rolf

UPDATED: Typo in code.

Replies are listed 'Best First'.
Re^7: OOP: ->Coderef for calling Private Methods (possibilites?)
by ccn (Vicar) on Dec 13, 2008 at 20:27 UTC
    > How does Perl know which package the subroutine is in?

    It concerns calling by name only. If perl has a reference to code it just executes it. There is no need to determine a package for the call. And the sub itself knows the package it belongs to.

      I think it's clear that I talk about misleadingly short docs.

      Documentation has to be clear for any user, even without deeper knowledge of perl internals and the need to run experiments!

      Cheers Rolf