Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:101575
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.196 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CACXBjugZrXXORVsaFhJzRO_WEiUXnVEHBBuHZysPUGRN6Ls7nw@mail.gmail.com>
References: <CAEUnE0d+rHG-Rvjt7QAN6x6L+BP5Yb_cz8sGuOFDOkx-kCehkA@mail.gmail.com>
 <9a3a8760-f65a-a5c0-b318-1830a9a986c3@gmail.com> <CAH0Uv3H_DEPZ5HmaKGe08_DMrzndBz7ofJTUgeb4f66zeaj1EA@mail.gmail.com>
 <9352F6DF-9940-49A2-9B1D-FA9258E9738E@lerdorf.com> <bb4579ba-2e09-4199-a871-be4428a1ee2d@lsces.co.uk>
 <ee3d2ffc-a72c-78f3-281b-dd029c706105@gmail.com> <CAEUnE0eShfm4kZck=2gBef6cgU6DdrKggtotUK+Jyk6uPYOYFg@mail.gmail.com>
 <CACXBjugZrXXORVsaFhJzRO_WEiUXnVEHBBuHZysPUGRN6Ls7nw@mail.gmail.com>
Date: Wed, 10 Jan 2018 07:27:55 -0600
Message-ID: <CAEUnE0ce2HRfsKOy_=NSnrENUnGpB4m-C=cMQFV93MgbaMguOQ@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="94eb2c18931ed0ea3d05626bffbb"
Subject: Re: [PHP-DEV] [RFC][DISCUSSION] Strong Typing Syntax
From: tendoaki@gmail.com (Michael Morris)

--94eb2c18931ed0ea3d05626bffbb
Content-Type: text/plain; charset="UTF-8"

On Wed, Jan 10, 2018 at 12:53 AM, Rasmus Lerdorf <rasmus@lerdorf.com> wrote:

>
> The difference here is that the end syntax is something like 10% of the
> problem. 90% of it is fitting it into the engine in an efficient manner
> giving that it is affecting the very core of the engine. An RFC on this
> issue that doesn't address the bulk of the problem isn't all that helpful.
>
>
It makes absolutely NO sense to do that 90% of the work to have it all
burned up when the proposal fails to carry a 2/3rds vote because the syntax
is disliked.

Also, drawing the architectural drawings for a skyscraper is also like only
10% of the work, but it's a damn important 10%.

That the implementation will be a major pain in the ass to do is all the
more reason to create and pass a planning RFC before doing any related
code/implementation RFC's. It will encourage people to do the research to
try to figure out how to get this done because they know the syntax is
approved and they aren't fiddling around in the dark trying to figure out
how to do something that may not be accepted for inclusion at all, which is
a huge waste of time.

--94eb2c18931ed0ea3d05626bffbb--