I've discussed a user-level deprecation notice for 5.3 with Stas; we'll see whether that makes it in or not. I'll keep the list updated with any news on this front. Also, currently we don't have a timeframe for the release of 2.0. It may very well make sense to have a dependency on 5.3 at that point, depending on how far from now the release is and when 5.3 is released and what adoption it sees. In any case, we realize that backwards compatibility is a very critical factor to take in to account in our decisions, so we'll be discussing changes such as these with the community before making decisions that affect compatibility.
,Wil > -----Original Message----- > From: Bill Karwin [mailto:[EMAIL PROTECTED] > Sent: Friday, July 18, 2008 8:52 AM > To: [email protected] > Subject: Re: [fw-general] Zend_Deprecation is ready for community > review. > > > > > Lars Strojny-2 wrote: > > > > In PHP 5.3 we will even have E_DEPRECATED as an error level. > > > > I saw that, but I had the understanding that user-space code is > supposed to > trigger only the "USER" error levels, E_USER_WARN, E_USER_NOTICE, and > E_USER_ERROR. I assume the others are reserved for use by PHP > internals. > The example given is that E_DEPRECATED will be triggered if you try to > use > the is_a() function. > > Also, until ZF officially requires PHP 5.3 as a minimum version, ZF > should > not make use of features that are new in that version. > > Regards, > Bill Karwin > -- > View this message in context: http://www.nabble.com/Zend_Deprecation- > is-ready-for-community-review.-tp18513175p18532311.html > Sent from the Zend Framework mailing list archive at Nabble.com.
