Hi all, On Sat, Feb 21, 2015 at 9:58 AM, Niklas Keller <m...@kelunik.com> wrote:
> 2015-02-21 1:23 GMT+01:00 Yasuo Ohgaki <yohg...@ohgaki.net>: > > > > Hi all, > > > > On Sat, Feb 21, 2015 at 2:55 AM, Sara Golemon <poll...@php.net> wrote: > > > > > Announcing this in its own thread: > > > https://wiki.php.net/rfc/reserve_even_more_types_in_php_7 > > > > > > This RFC acts as an addition to Levi's > > > https://wiki.php.net/rfc/reserve_more_types_in_php_7 by creating a > > > forum for voting on additional types not included in his RFC: > > > resource, object, scalar, mixed, numeric > > > > > > > We should have reserved these. IMHO. > > Yes, it breaks. However, sooner is better. > > > > People don't just use PHP7. We may try to promote these > > changes now. We still have time. > > > > Regards, > > > > -- > > Yasuo Ohgaki > > yohg...@ohgaki.net > > > Resource is used quite often: > > https://github.com/search?l=php&q=class+Resource&ref=searchresults&type=Code&utf8=%E2%9C%93 > Unfortunately, GitHub doesn't allow a search for "class Resource " for > better results. > > Google knows about 600 occurrences: > https://www.google.de/?#q=site:github.com+%22class+resource%22+php > One more popular example usage: > > https://github.com/phacility/phabricator/blob/master/externals/balanced-php/src/Balanced/Resource.php > > Just to throw some numbers in. We may buy some time. We may announce it by PHP 7.0. (E_STRICT perhaps?) Introduce new reserved words in PHP 7.X. (E_ERROR/E_COMPILE_ERROR whichever is appropriate) Sooner announcement is better, then introduce. It would work better. Regards, -- Yasuo Ohgaki yohg...@ohgaki.net
