Re: Migration guidelines
| From: | Pierre-Alain Joye | Date: | Fri, 06 Feb 2004 09:09:44 +0000 |
| Subject: | Re: Migration guidelines | ||
| References: | 1 | Groups: | php.pear.qa |
| Request: | Send a blank email to pear-qa+get-493@lists.php.net to get a copy of this message | ||
Hello,
On Wed, 04 Feb 2004 21:14:03 +0100
tobias@schlitt.info (Tobias Schlitt) wrote:
> In general we should take care of the followning (in no specific
> order):
>
> - Usage of __construct/__destruct.
> In respect to BC, this should be left as is for the constructor (+ I
> generally have something personal against __construct()). The usage of
> __destruct seems not very regulatable.
In respect to BC? A true migration of a packge to php5 will require deep
change anyway, redirect BC to /dev/null ;). To be precised, I'm talking
about a PHP5 package but not about making a package works smoothly with
php5.
What do you have against __construct()?
> - Function definition.
> These defintions have to be changed in respect to & operator usage,
> private public, as well as additions for interfaces and abstract
> classes. A regulation of statics should be applied, too.
Why? I do not see what we have to regulate here. The '&' operator is
part of the 'smooth' migration.
> - We should set up some more naming conventions.
Please no more :) We have enough NC and I will hate to read the manual
every line I write.
> As PEAR has a couple of packages now, we should extract "common
> namings" for methods and definitifly define them. This will raise
> usability for PEAR pretty much.
Maybe a good thing, not sure we can get a compromise about that. ( We
will get our flamewars quota with this topic ;) )
> - The usage of __clone() should be defined.
> It should be essential to have a __clone method implemented.
Why? Again, I do not see why we have to use __clone.
> - __get and __set should be regulated, as well as the usage of __call.
(wonder) why?
> - The handling of type hinting should be regulated.
(Again)why??? It's so closed to each package/implementations/methods....
As a sidenote, can I put your attention (QA) on the upcoming 4.3.5
release? I did not see any reply, posts (on php-qa or here), bugs
reports, from any of you... Is it not the primary goal of the QA team?
pierre