Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:84795
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain kelunik.com from 81.169.146.162 cause and error)
MIME-Version: 1.0
In-Reply-To: <CAGH8S73k4vJVgr=bLtYNMKUq22=tGQSEW49UBEC=BtMPwf2DZg@mail.gmail.com>
References: <CANUQDCjK7F1H5PZeV4XXvbDOsmyYtG4P1fPH3QnKBuY9EM-JdA@mail.gmail.com>
	<CAGH8S73k4vJVgr=bLtYNMKUq22=tGQSEW49UBEC=BtMPwf2DZg@mail.gmail.com>
Date: Sun, 15 Mar 2015 03:07:16 +0100
Message-ID: <CANUQDCj0fnendabiCajOVZr6WLeOaaU+NYFuYSbr+ihY7-ArLg@mail.gmail.com>
To: Antonio Carlos Ribeiro <acr@antoniocarlosribeiro.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC][PRE-VOTE] In Operator
From: me@kelunik.com (Niklas Keller)

2015-03-15 2:48 GMT+01:00 Antonio Carlos Ribeiro <acr@antoniocarlosribeiro.=
com>:
> Niklas,
>
> I have to thank you for creating this RFC, I simply love it, every time I
> have to use in_array() I feel PHP misses an "in" operator. I cannot vote,
> but you have my spiritual support :)

Thanks for your feedback. :)

> Antonio Carlos Ribeiro
> acr@antoniocarlosribeiro.com
>
> (+55) 21-9-8088-2233 (celular TIM)
> (+55) 21-2556-3164 (fixo residencial)
>
> skype: antoniocarlosribeiro
>
> _______________
>
> I must say I find television very educational. The minute somebody turns =
it
> on, I go to the library and read a good book. (Devo dizer que acho televi=
s=C3=A3o
> muito educativo. Quando algu=C3=A9m a liga, vou =C3=A0 biblioteca e leio =
um bom
> livro.)
>
> (Groucho Marx)
>
>
> On Sat, Mar 14, 2015 at 9:54 PM, Niklas Keller <me@kelunik.com> wrote:
>>
>> Morning,
>>
>> I'd like to announce that I'll open the vote for the in operator later
>> that day.
>> You can find the RFC here: https://wiki.php.net/rfc/in_operator
>>
>> There was a small change: If the haystack is a string, integers are no
>> longer allowed as needle. This change was necessary so it's
>> consistently strict for both, array and string haystacks.
>>
>> Regards, Niklas
>>
>> --
>> PHP Internals - PHP Runtime Development Mailing List
>> To unsubscribe, visit: http://www.php.net/unsub.php
>>
>

I just adjusted the Backwards Incompatible Changes section, as class
constant and method names will no longer be affected due to the
context sensitive lexer dependency.

Regards, Niklas