Re: how to deal with php5 only packages

Joe Stump wrote:

I think there is nothing wrong if we politely disagree. You (and Lukas may be) have a more "let's use PHP 5 only if it is really necessary" my approach is the opposite. Why should I write something with an obsolete object model ? Just to re-write it from scratch in few months ?

I completely agree with this. I think new packages that are not deemed to be core/must-have packages should be able to be written in PHP5 (obviously the recent ErrorStack shouldn't require PHP5).

You dont have to rewrite your package from scratch when you want to use private/protected/public. If you start using specific stuff that cannot be handled with minimal effort with PHP4 or makes the solution for PHP5 inferior then I see it is valid. For example a package using simplexml or another php5 only package. Making sensible use of exceptions is another good reason. However the definition of sensible is still up in the air. For example __autoload() is nifty. But not having it in PHP4 just means that the user has to manually make sure the necessary class is included. Interceptors are cool and maybe they are not reliable enough in PHP4, but for example in MDB2 they would simply make things more convinient. So you can use alot of PHP5 only features while still staying compatible to PHP4. regards, Lukas Smith smith@backendmedia.com _______________________________ BackendMedia www.backendmedia.com berlin@backendmedia.com Linn Zwoch Smith GbR Pariser Str. 44 D-10707 Berlin Tel +49 30 83 22 50 00 Fax +49 30 83 22 50 07