> > The fact that this use of PHP is documented in the manual as a feature > www.php.net/manual/en/**language.oop5.basic.php<http://www.php.net/manual/en/language.oop5.basic.php> > > And mentions that it will elicit a E_STRICT error - does not indicate that > it would be DEPRECATED, I'm assuming that has been documented for years, > and only recently (a year or two) has the E_STRICT comment been added. > There is also no real Justification for the E_STRICT message = see > suggestion at end.. >
I stand corrected, I said that (AFAIR) is an undocumented feature, but as you pointed out, it is documented since (at least) 2004: http://svn.php.net/viewvc/phpdoc/en/trunk/language/oop5/basic.xml?view=markup&pathrev=166424 (there is a typo here, so it is called a psudo variable) And an example was added in 2005: http://svn.php.net/viewvc?view=revision&revision=178495 by sean (funny commit comment: 'document seemingly-odd $this behaviour'). The E_STRICTs were added to the examples in 2009: http://svn.php.net/viewvc?view=revision&revision=288217 This doesn't really change my opinion, but it means that there could be more people using this feature than I/we assumed. Given the fact that this already spits E_STRICT(and E_STRICT is part of E_ALL since 5.4) and both E_STRICT and E_DEPRECATED is disable in our php.ini-production, I would say that changing this from E_STRICT to E_DEPRECATED has no direct impact to the userland. But we can use this change to sample the people using this feature and based on the feedback we can decide whether we want to keep this or remove it for the next version. So my opinion is that we should stick to the vote and deprecate this feature but update the RFC and remove the part removing it in the next version. -- Ferenc Kovács @Tyr43l - http://tyrael.hu
