Re: how to deal with php5 only packages

On Jun 16, 2004, at 7:24 PM, Lukas Smith wrote:

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.

That is my point. Sensible use of PHP 5 is really something vague and subjective. If there is a clear rule against PHP 5 for new packages I will wait the official ruling. Till then I don't see why I should use PHP 4 unless is really necessary. To you SQLite is not a good reason, to me it is. For one I get rid of another dependency...

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.

Yes but it requires more and planning and time to adapt a decent class to an inferior object model. It doesn't make sense to me as PHP 5 is already out and available. Didn't we agree that the proposal of PHP 5 packages was fine as long as E_STRICT compliant and not stable till PHP 5 is ? You are free to recommend otherwise but I don't think that the approach "PHP 4 works, so why switch" is very progressive. Regards David Costa

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