Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:84775
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.220.176 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CABBJUpeLjoZknCjzsBX3WzcgrFSh=cZEUEDVRdNvZ7nJYt=vDA@mail.gmail.com>
References: <CABBJUpdf-cSBc2y_Urh_BU4BJo3nEY1nLZsyVEU+UBso22uGgQ@mail.gmail.com>
	<BLU436-SMTP145E589F1C17580C1F87BA5E2040@phx.gbl>
	<CABBJUpeLjoZknCjzsBX3WzcgrFSh=cZEUEDVRdNvZ7nJYt=vDA@mail.gmail.com>
Date: Sat, 14 Mar 2015 15:15:03 +0300
Message-ID: <CA+9eiLvBWSpSdwNa1ZrEfiKDUdNhfroY4qU88qeuLEHU-SaJBQ@mail.gmail.com>
To: Laruence <laruence@php.net>
Cc: PHP Internals <internals@lists.php.net>, Bob Weinand <bobwei9@hotmail.com>
Content-Type: multipart/alternative; boundary=001a1136b57416bc0905113e91a5
Subject: Re: [PHP-DEV] Drop Multiply VM kind support
From: dmitry@zend.com (Dmitry Stogov)

--001a1136b57416bc0905113e91a5
Content-Type: text/plain; charset=UTF-8

In general, it's possible to implement necessary function for GOTO executor
as well.
It's just not trivial.

Thanks. Dmitry.
On Mar 14, 2015 3:06 PM, "Xinchen Hui" <laruence@php.net> wrote:

> Hey:
>
> On Sat, Mar 14, 2015 at 8:01 PM, Bob Weinand <bobwei9@hotmail.com> wrote:
> >> Am 13.03.2015 um 05:01 schrieb Xinchen Hui <laruence@php.net>:
> >>
> >> Hey:
> >>
> >>     We have CALL SWITCH GOTO vm kind supports for long time.
> >>
> >>     And we use CALL for default.
> >>
> >>     SWITCH GOTO seems useless now, and brings us some troubles while
> >> maintaining .
> >>
> >>     And also could make some extension unable to work, like in phpdbg:
> >>
> >>              PHPDBG_G(vmret) =
> execute_data->opline->handler(execute_data);
> >>
> >>
> >>     So, maybe it's time for us to remove GOTO and SWITCH at all?
> >>
> >> thanks
> >>
> >> --
> >> Xinchen Hui
> >> @Laruence
> >> http://www.laruence.com/
> >
> > Not sure whether it's useless, I'm not exactly aware of the performance
> differences.
> > But we would have to add some proper build-time check for phpdbg whether
> we're in CALL mode or not. [when you're using phpdbg on that machine, you
> probably aren't in a high-performance production environment anyway.]
> >
> > (Like with a clean #error message etc.)
> >
> After the latest fix by Dmitry, there will be no need for that.
>
> because, if in non CALL mode, phpdbg won't be able to built anymore.
>
> thanks
> > Bob
>
>
>
> --
> Xinchen Hui
> @Laruence
> http://www.laruence.com/
>

--001a1136b57416bc0905113e91a5--