Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:105703
MIME-Version: 1.0
References: <CAF+90c_DEpQpLe7M_g5vQZmxHD-e5fEyxubpH_99vhKYvkDWYA@mail.gmail.com>
 <F620A9B4-C930-4855-82D0-F9EF9896253B@gmail.com> <CAG9XoMQLKHv6s79yMRd2SDWEoFCxy+wsbJG+AZ7Hjx+OXZwbSw@mail.gmail.com>
In-Reply-To: <CAG9XoMQLKHv6s79yMRd2SDWEoFCxy+wsbJG+AZ7Hjx+OXZwbSw@mail.gmail.com>
Date: Tue, 14 May 2019 16:42:26 +0200
Message-ID: <CAF+90c-poOY+S+YsJkY3o=5aunwPTr1OGRTixjNQuHDJ8Bo3kQ@mail.gmail.com>
To: Benjamin Morel <benjamin.morel@gmail.com>
Cc: Steven Wade <stevenwadejr@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000097041b0588da0bcd"
Subject: Re: [PHP-DEV] Add get_mangled_object_properties()
From: nikita.ppv@gmail.com (Nikita Popov)

--00000000000097041b0588da0bcd
Content-Type: text/plain; charset="UTF-8"

On Tue, May 14, 2019 at 4:29 PM Benjamin Morel <benjamin.morel@gmail.com>
wrote:

> I like the explicitness of the proposal, but only if performance is as
> good as (array) cast. One of the reasons we use casting to array in
> libraries is not only to access all properties at once, but also because
> it's fast as it's implemented as an opcode and not a function call. Would
> this function come with its own opcode, like strlen() / gettype() / etc.?
>
> Ben
>

I don't think an opcode is worthwhile in this case, because the primary
cost is in constructing the property array. On this micro-benchmark
https://gist.github.com/nikic/f592686c75d8d34d82ddc5900b598199 the results
are:

array cast: float(0.39156699180603)
get_mangled_object_vars(): float(0.41520500183105)

So no relevant difference in performance.

Nikita

--00000000000097041b0588da0bcd--