Hi Kalle, hi Matthew > We stopped trying to future proof code by soft > reserving after PHP6 turned out to be nothing and most of the features > were ported to PHP5.3.
I wanted to reduce resistance to the RFC I'm planning because of BC breaks in a minor version. For this reason I would personally prefer to have the BC break in a major version but I'm ok with either approach. It's worth noting that we did indeed register some keywords in PHP 7 before they were used: https://wiki.php.net/rfc/reserve_even_more_types_in_php_7 > An enum implementation seems like something that almost certainly > will make it into the language in the next 4 years, given PHP’s > gradual adoption of features that already exist Hack (e.g. attributes, > constructor property promotion). Yes, this is my sentiment too. Ilija -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
