Re: Migration guidelines
| From: | Greg Beaver | Date: | Wed, 04 Feb 2004 23:45:53 +0000 |
| Subject: | Re: Migration guidelines | ||
| References: | 1 | Groups: | php.pear.qa |
| Request: | Send a blank email to pear-qa+get-486@lists.php.net to get a copy of this message | ||
Hi,
Everything looks fine except for what I've noted below
Tobias Schlitt wrote:
- The usage of __clone() should be defined. It should be essential to have a __clone method implemented.default __clone() is good enough for most packages - a bit-for-bit copy.
- Either something should be build around or the usage should be regulated for __autoload(). I like this feature pretty much and I guess this could be implemented in one piece for the complete PEAR framework. That'd be cool! :)I really dislike __autoload() because it can only be implemented once, and cannot be changed. I am strongly against its use in PEAR - this should be an application-level function, not a package-level one.
- __get and __set should be regulated, as well as the usage of __call.The main thing that needs to be decided is how to document them properly, both in-code and out.
- The handling of type hinting should be regulated.I'm not sure I see why - type hinting is internal to the method/function that uses it. Greg