There have been some last-minute concerns raised about var being reserved "for future usage". My intent was that var couldn't be used for function/class names IN CASE it was re-used in the future, but not encouraging it to be re-used. I'd assume that reusing it would require a separate RFC to pass by a 2/3rds margin.
Does anyone disagree with this interpretation or feel that it should be explicitly stated? Would anyone change their vote from NO to YES if "for future usage" was removed (but "reserving it" was kept in)? Would anyone change their vote from NO to YES if the question of "reserving it" could be voted on separately? If so, and we can stop the vote to make these changes, I'd strongly prefer to do so. I'd hate for three words to sink the entire RFC. (My apologies if this belongs in the discussion thread instead) Regards, Colin On Thu, Mar 24, 2016 at 8:40 AM Colin O'Dell <colinod...@gmail.com> wrote: > Hello everyone, > > It has been two weeks since discussion started on the RFC to deprecate and > eventually remove the "var" keyword (and one month since the idea was > originally proposed). > > This RFC has therefore been moved to the "In Voting" state. Voting will > begin immediately and will end in one week. > > You can find the full RFC (including the proposed patch and automatic > upgrade tool) here: https://wiki.php.net/rfc/var_deprecation > > I encourage everyone to read the RFC and cast your vote towards whichever > option you feel is the best for the language and the community. > > Regards, > > Colin O'Dell >
