Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:81088
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.178 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CABBJUpd39fFT0irD8UWYWK1pey=PNL6ujbhfRZgpsxnsKOmoWA@mail.gmail.com>
References: <54C12DD8.7020800@lerdorf.com>
	<5er2cat2lpaq6bs6tmpapllcbq6lbcf0te@4ax.com>
	<CA+9eiLvAYwsWkWOvGnF+QcCCDdaV4ku1OT5nKR1PKs66Kdz9jA@mail.gmail.com>
	<3de5cah741q5ukqgqa60p71c3u0ipu0465@4ax.com>
	<4vg5cad3uavfkv4qr8604sri16h6pip4f5@4ax.com>
	<CA+sv8zBiDQnDETJLfzi1_AzDrotTCVwdM9Di-ks_mTt3gv0AVg@mail.gmail.com>
	<CA+sv8zCHymPiKMixXS=bRnfEgnisGK5khDU7PtoiOq=LdGxmOA@mail.gmail.com>
	<CA+sv8zAFVck42OXONy29rFUfkJeNTOmFRrEk-CwGbEn5dzt8EQ@mail.gmail.com>
	<CABBJUpd39fFT0irD8UWYWK1pey=PNL6ujbhfRZgpsxnsKOmoWA@mail.gmail.com>
Date: Sat, 24 Jan 2015 12:43:22 -0500
Message-ID: <CA+sv8zCUPqqEeoORrEK=A8Ruqvx=ZTLq6NyRt05B+M9ZMvSfbw@mail.gmail.com>
To: Xinchen Hui <laruence@php.net>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e0149c0a006f753050d697174
Subject: Re: [PHP-DEV] Re: PHP7 Homework for everyone reading this list
From: jrbasso@gmail.com (Juan Basso)

--089e0149c0a006f753050d697174
Content-Type: text/plain; charset=UTF-8

I see. Shouldn't this BC break be added on the UPGRADING file too? I can
open a PR if necessary.

On Sat, Jan 24, 2015 at 12:40 PM, Xinchen Hui <laruence@php.net> wrote:

> Hey:
>
> On Sun, Jan 25, 2015 at 1:26 AM, Juan Basso <jrbasso@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
>
> >
> > On Sat, Jan 24, 2015 at 12:53 AM, Juan Basso <jrbasso@gmail.com> wrote:
> >
> >> This is not a segfault, but another issue exclusive from PHP 7
> >> https://bugs.php.net/bug.php?id=68897
> >>
> >> On Fri, Jan 23, 2015 at 11:54 PM, Juan Basso <jrbasso@gmail.com> wrote:
> >>
> >>> I found another segment fault on PHP 7 during CakePHP 3 tests. I
> reported
> >>> the issue on https://bugs.php.net/bug.php?id=68896
> >>>
> >>> On Fri, Jan 23, 2015 at 5:01 PM, Jan Ehrhardt <phpdev@ehrhardt.nl>
> wrote:
> >>>
> >>>> Jan Ehrhardt in php.internals (Fri, 23 Jan 2015 22:18:50 +0100):
> >>>> >Dmitry Stogov in php.internals (Fri, 23 Jan 2015 17:54:45 +0400):
> >>>> >>"master" branch.
> >>>> >
> >>>> >propro, raphf and pecl_http do not compile with the master branch.
> >>>> >You'll have to checkout the phpng branch. These extensions did
> compile
> >>>> >and load:
> >>>> >
> >>>>
> https://phpdev.toolsforresearch.com/php-7.0.0-dev-nts-Win32-VC11-x86.htm
> >>>> >
> >>>> >Build:
> >>>> >
> >>>>
> https://phpdev.toolsforresearch.com/php-7.0.0-dev-nts-Win32-VC11-x86.zip
> >>>>
> >>>> The TS build is very much alike:
> >>>> https://phpdev.toolsforresearch.com/php-7.0.0-dev-Win32-VC11-x86.htm
> >>>> https://phpdev.toolsforresearch.com/php-7.0.0-dev-Win32-VC11-x86.zip
> >>>>
> >>>> What you cannot see in phpinfo() is that php7apache2_4.dll and even
> >>>> php7apache2_2.dll also compile fine.
> >>>>
> >>>> >Maybe there are other PECL extension that have PHP7 branches,
> unknown to
> >>>> >you and me.
> >>>>
> >>>> Jan
> >>>>
> >>>> --
> >>>> PHP Internals - PHP Runtime Development Mailing List
> >>>> To unsubscribe, visit: http://www.php.net/unsub.php
> >>>>
> >>>>
> >>>
> >>
>
>
>
> --
> Xinchen Hui
> @Laruence
> http://www.laruence.com/
>

--089e0149c0a006f753050d697174--