in reply to Re^3: multiple method calls against the same object, revisited
in thread multiple method calls against the same object, revisited
Yeah, you pretty much just wrote what I did in RFC: Class::Proxy::MethodChain. Now make a root node about it, get some well-reasoned skeptic comments, mull over it for a year or so, and then write the code I posted in the root node of this thread. :-) As I said, I've gone through at least a dozen approaches and logical next steps with this thing and it's not likely you'll be able to surprise me as long as you stick to the obvious ideas — sorry.
The problem with this group of solutions, as others said in that thread and as I have come to understand with the experience gained since that node (see Mutator chaining considered harmful), is that method chaining is not a good idea.
Makeshifts last the longest.
|Replies are listed 'Best First'.|
Re^5: multiple method calls against the same object, revisited
by eric256 (Parson) on Dec 28, 2004 at 23:14 UTC