in reply to Re^3: multiple method calls against the same object, revisited
in thread multiple method calls against the same object, revisited

How is this a gain over Class::Null? For more info, take a look at The Null Mull (or, when OO needs more O)

Being right, does not endow the right to be rude; politeness costs nothing.
Being unknowing, is not the same as being stupid.
Expressing a contrary opinion, whether to the individual or the group, is more often a sign of deeper thought than of cantankerous belligerence.
Do not mistake your goals as the only goals; your opinion as the only opinion; your confidence as correctness. Saying you know better is not the same as explaining you know better.

  • Comment on Re^4: multiple method calls against the same object, revisited

Replies are listed 'Best First'.
Re^5: multiple method calls against the same object, revisited
by eric256 (Parson) on Dec 28, 2004 at 19:30 UTC

    I'm sorry I don't see how this even compares to that. The function of this is to wrap methods so that they always return a reference to the object. The Class::Null make an object that handles all method calls gracefully. I don't see how the two are related other than they pertain to method chaining, however they deal with different parts, this wraps the method call to force it to chain, that wraps it to handle error cases. The two could be combined to supply some extra method chaining sugar though.


    ___________
    Eric Hodges
[reply]

In Section Cool Uses for Perl