Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:89916
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.169 as permitted sender)
MIME-Version: 1.0
Sender: tomac120@gmail.com
In-Reply-To: <CAGa2bXa9=bQkWHE-yrp73WZ0t=rhzSrr+UD0jF7Spq1sW5NJuw@mail.gmail.com>
References: <CANmB6N8de7Hrs0VZOYoy9tSq9Jh7TvheBKX--qhLoc5Jf562wQ@mail.gmail.com>
	<56811E49.1040106@php.net>
	<CAGTDVF5RAxkExV2WDfBdeNb5x+5+aQDYkSAn+2wRkbxKyYVoBw@mail.gmail.com>
	<CAGTDVF6Pbq3vKcoHu+cSPB9k-L=G_wCRAxBCBBHF_A2CPNkWjw@mail.gmail.com>
	<CAGa2bXa8U_rFZNzdJ_fjVWkvS+p3sgY0G6gQUV_+p8Ptdwr_GQ@mail.gmail.com>
	<CAGa2bXa9=bQkWHE-yrp73WZ0t=rhzSrr+UD0jF7Spq1sW5NJuw@mail.gmail.com>
Date: Mon, 28 Dec 2015 18:23:29 -0500
Message-ID: <CAGTDVF5hFQyB=b30fP6OCuMiOWHxZxzOSwJzRc+mYTz91=Vg-g@mail.gmail.com>
To: Yasuo Ohgaki <yohgaki@ohgaki.net>
Cc: =?UTF-8?Q?Fran=C3=A7ois_Laupretre?= <francois@php.net>, 
	"internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e01229de0b96a280527fd9771
Subject: Re: [PHP-DEV] Make strict mode more strict?
From: ejrx7753@gmail.com (Elijah Johnson)

--089e01229de0b96a280527fd9771
Content-Type: text/plain; charset=UTF-8

Hi (all),

On Mon, Dec 28, 2015 at 3:40 PM, Yasuo Ohgaki <yohgaki@ohgaki.net> wrote:

> Hi all,
>
> On Tue, Dec 29, 2015 at 5:28 AM, Yasuo Ohgaki <yohgaki@ohgaki.net> wrote:
> > Object(class) is type, so it makes sense checking class consistency. If
> we
> > check object's class, not only the class but also ancestor classes
> should be
> > checked. This may affect performance.
> > I'm not sure if this worth the effort.
>
> It sounds negative, so I correct this.
>
> Since we have class type hint, it better to support class check. IMO.
> Almost all cases are simple class equality check. So it wouldn't hurt
> performance much, I suppose.
>
> Regards,
>
> --
> Yasuo Ohgaki
> yohgaki@ohgaki.net
>

I think that it would be worthwhile to get either a RFC or some test code
on this, the latter depending on how you would assess the difficulty. The
feature itself has a huge demand and goes along the lines of current
development.

If something could be developed, then we could assess performance. I would
estimate it to be small, however in any case the feature is optional. We're
not anymore considering to increase the size of the z-val.

The feature has 2 stages, one of which would be drastically easier to
implement and would show us about performance.

Stage 1 - typing only objects already set by comparing classes upon
assignment, if set a particular mode

Stage 2 - Adding some form of language hint, which will require a parser
and some method of storing the class hint for null objects. The latter has
a proposed solution not sounding hard to implement, but modifying the
parser sound like a more difficult step.

--089e01229de0b96a280527fd9771--