Re: [PEPr] Comment on PEAR::PEAR_Delegator
| From: | lingwitt at bellsouth dot net | Date: | Tue, 22 Feb 2005 14:08:22 +0000 |
| Subject: | Re: [PEPr] Comment on PEAR::PEAR_Delegator | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-36338@lists.php.net to get a copy of this message | ||
Any thoughts?
On 19 Feb 2005, at 13:19, Herr Witten wrote:
Herr Witten (http://pear.php.net/user/lingwitt) has commented on the proposal for PEAR::PEAR_Delegator. Comment: "or even automatically delegated on demand (very cool feature to have)." This would be neat, but it seems messy. The main Delegator.php file could have these methods simply load and add the proper extension delegate. Then they would call the delegated method from then on. Yet, how should the extension code be split up? Should each method have its own extension file? Here is the list of extensions so far: //possible extensions getAllDelegates getDelegate is_a respondsToMethod //Current extensions hasDelegateExact getDelegateExact getDelegateRecursive getDelegateRecursiveExact getDelegateForMethodRecursive getDelegateForMethodRecursiveExact getDelegateForMethodFirst removeDelegateRecursiveExact uncacheMathod Proposal information: http://pear.php.net/pepr/pepr-proposal-show.php?id=210