Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:91073
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain fredemmott.co.uk from 209.85.160.179 cause and error)
Content-Type: multipart/alternative; boundary="Apple-Mail=_2DA5B687-44C0-4F0F-B345-006B4F19F9DE"
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
In-Reply-To: <CANaX5neqdCG=MkWppTGM=CWhP9pLirJoyRkK5QDBOevHAt3ssg@mail.gmail.com>
Date: Wed, 3 Feb 2016 17:37:08 -0500
Cc: Sara Golemon <pollita@php.net>,
 Matt Prelude <me@mprelu.de>,
 PHP internals <internals@lists.php.net>
Message-ID: <BA9718E8-BCB2-450E-9204-B26F257B34CA@fredemmott.co.uk>
References: <CANaX5nf4eDSVaYg=HygRO-vK7r9yAvdhzoTUOFHT1LHUjpQjgw@mail.gmail.com> <CA+kxMuQCXB2VssedW9E=kvB4UfM+VbkWFHAZ4BFz9O7cWZA5Ag@mail.gmail.com> <56B233C0.10301@mprelu.de> <CAESVnVo6dM2N4KuA144pWkGe53ggy_rRF690QViVX5hmCc5D5Q@mail.gmail.com> <CANaX5ncq5JX704G66wWcYOWMKDkkd=CqQuEQ2DT5a32qiM1P0A@mail.gmail.com> <216F291E-F174-4E07-B650-DC9A63C07F61@fredemmott.co.uk> <CANaX5neqdCG=MkWppTGM=CWhP9pLirJoyRkK5QDBOevHAt3ssg@mail.gmail.com>
To: Davey Shafik <davey@php.net>
Subject: Re: [PHP-DEV] [RFC] Add PHP_ENGINE Constant
From: fred@fredemmott.co.uk (Fred Emmott)

--Apple-Mail=_2DA5B687-44C0-4F0F-B345-006B4F19F9DE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Fair enough - though I=E2=80=99m not convinced that it would be =
effective: if successful, it would allow people to do =
90=E2=80=99s-browser-sniffing-style if ($engine !=3D=3D =E2=80=98my =
favorite=E2=80=99) throw Exception(=E2=80=99sorry, not supported =
yet=E2=80=99);, so it seems fairly likely that implementations would end =
up lying about it (and yes, deviating from the spec) in a few years =
anyway.

As a side note, AFAIK HippyVM isn=E2=80=99t being actively developed =
(https://twitter.com/HippyVM/status/634347845957627904 =
<https://twitter.com/HippyVM/status/634347845957627904>)


> On Feb 3, 2016, at 5:29 PM, Davey Shafik <davey@php.net> wrote:
>=20
> Currently, HippyVM doesn't even _have_ a version constant. Because =
it's trying to pretend to be PHP. Having a "YOU MUST FILL THESE =
CONSTANTS WITH YOUR OWN RUNTIMES DATA" in the spec is intended to help =
that situation.
>=20
> Right now, there's no way to tell what version of HippyVM you're =
running on, and to even check that you're using Hippy you need to check =
for E_HIPPY_WARN.
>=20
> We have a chance to standardize, and "mandate" that the information is =
exposed explicitly, and done so consistently.
>=20
> On Wed, Feb 3, 2016 at 5:14 PM, Fred Emmott <fred@fredemmott.co.uk =
<mailto:fred@fredemmott.co.uk>> wrote:
>=20
>> On Feb 3, 2016, at 2:00 PM, Davey Shafik <davey@php.net =
<mailto:davey@php.net>> wrote:
>>=20
>> On Wednesday, February 3, 2016, Sara Golemon <pollita@php.net =
<mailto:pollita@php.net>> wrote:
>>=20
>> Unfortunately Sara, the types of things you generally have to work =
around
>> are minor things, like differences in DOM, or the inability to =
json_encode
>> DateTimeImmuteable
>=20
>=20
>=20
> It seems like the main thing this RFC would change is that you could =
easily do =E2=80=9Cif ($engine !=3D=3D =E2=80=98php=E2=80=99)=E2=80=9D - =
but for almost all the examples I can think of, and yours, what=E2=80=99s =
actually needed is if "($engine =3D=3D=3D =
=E2=80=98specific_engine_that_needs_a_workaround=E2=80=99)=E2=80=9D, so =
I don=E2=80=99t see a benefit over using HHVM_VERSION or similar.
>=20
> The one exception I can think of is if someone=E2=80=99s =
reimplementing phpinfo() or similar.
>=20
> Regards,
>  - Fred
>=20


--Apple-Mail=_2DA5B687-44C0-4F0F-B345-006B4F19F9DE--