Mike,
Back to the subject,:
> It is indeed different but ever so slightly, a for loop in this case cannot
> handle a single argument of true and would cause a parse error.
> Therefore for ("PHP" in ["PHP, "C", "Java"]) could be handled differently.
> Again, my main point is that due to other languages the in
> operator itself also correlates to for ($var in $container), I understand
> having an additional RFC but this is indeed the place for
> discussion of such things.
Agree, but maybe a RFC for "in" operator and a follow up RFC to allow
"in" on "for" context could be a win/win here as long as one feature
doesn't block each other?
2015-01-20 11:10 GMT-03:00 Marcio Almada <marcio.w...@gmail.com>:
> Mike,
>
>> Also FYI - in the future please try not to top post and instead post under
>> where you are commenting as it makes it more difficult for
>> people coming later to the thread to see the scope of the conversation.
>
> Thanks for the tip! I read to "do not top post" on the guidelines but
> had no clue what it meant until now xD
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
