I see. I guess that's fine. I opened a PR for CakePHP to update the code and avoid this.
Thanks. On Sat, Jan 24, 2015 at 12:47 PM, Nikita Popov <nikita....@gmail.com> wrote: > On Sat, Jan 24, 2015 at 6:40 PM, Xinchen Hui <larue...@php.net> wrote: > >> Hey: >> >> On Sun, Jan 25, 2015 at 1:26 AM, Juan Basso <jrba...@gmail.com> wrote: >> > I step in another failing test that I would like to confirm if that is >> an >> > issue or it was an accepted backward incompatibility due the phpng (I >> > couldn't find anything on the RFC and the UPGRADING regarding that). >> > >> > Here is the code: http://3v4l.org/h7TEV >> > >> > The issue happens when the variable used to split data using list() is >> also >> > part of the variables that will receive the values. In the case of my >> > example, $data contains the data to be splitted and also will receive >> the >> > first value. >> > >> > Is that an issue or BC break? >> this is a knew BC break, please read "Changes to list()" section in >> the AST RFC https://wiki.php.net/rfc/abstract_syntax_tree >> >> thanks >> > > We also document this on http://php.net/list: > > Modification of the array during list() execution (e.g. using list($a, > $b) = $b) results in undefined behavior. > > If we want, we could make this defined behavior (we would have to disable > CV optimization on the $b fetch). I don't really care personally. > > Nikita >
