Re: Re: New thread - Template base class design
| From: | Lukas Smith | Date: | Fri, 11 Jun 2004 16:14:49 +0000 |
| Subject: | Re: Re: New thread - Template base class design | ||
| References: | 1 2 3 4 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-30502@lists.php.net to get a copy of this message | ||
Jackson Miller wrote:
On Friday 11 June 2004 10:43, Paul M Jones wrote:Not at all. This stuff will work with PHP5 no problem. We are just not leveraging PHP5 specific features in anything but optional features (for example MDB2 works with PHP4 and PHP5 but provides a PHP5 only iterator interface based class). PHP5's adoption is first and foremost determined by how stable and trusted it is and this remains to be seen. However I dont see a point in forcing users over to PHP5 just by using one of the PHP5 goodies (like marking properties as private instead of just var) which dont make anything better (yes of course its nice to technically enforce stuff like private but it certainly doesnt change the user experience if the user follows the API as documented). 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 07Agreed; the initial solution should be primarily PHP4 based, with nods to PHP5 compatibility that don't break PHP4 workings, and should not become PHP5 only until PHP5 is widely universally deployed.The catch-22 here is is that PHP5 adoption in some shops will be determined by PEAR package availability.