Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:107072
Message-ID: <BAB25C60-17E9-4287-9686-04F2FAD69A56@newclarity.net>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_C58FABE4-A770-4189-9B1D-F1EDCBE7CA6F"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Fri, 13 Sep 2019 02:47:07 -0700
In-Reply-To: <CABdc3WpPRx=znZsqG1uy97wehW1Q9J_Goo7mkp8x6oDyWDSbZw@mail.gmail.com>
Cc: Arnold Daniels <arnold.adaniels.nl@gmail.com>,
 PHP Internals <internals@lists.php.net>
To: =?utf-8?Q?Micha=C5=82_Brzuchalski?= <michal.brzuchalski@gmail.com>
References: <CABdc3Wpit02=BqvVE85ciw9qo3UYc2LBatOy23yFk5z+quZ2rw@mail.gmail.com>
 <CANS-=peR=rcZeHcRvZFxJPDsA402MKv_BxZ=ftU=Zo8Nad4CdQ@mail.gmail.com>
 <CABdc3WravK6Xgqd9zcskdmVAxO+ewekXB=HsSc56+HVfcWDa+g@mail.gmail.com>
 <74C03BB1-28DF-4694-A91D-2516C545F8B2@gmail.com>
 <3CA484B0-BCA3-4A2B-B2A6-8B845F9C462B@newclarity.net>
 <CANZOY=AMc6rj1s-GLXUr1X72LHBxpROzOV5=_AT-wfuDOdSFAg@mail.gmail.com>
 <2CA1F9C5-AC54-4E45-AE9E-20BB32BD7093@newclarity.net>
 <CABdc3Wq+iL_AH=bLFSvd8qEkZ780r4EZtSueav9ooRUy2Avd3A@mail.gmail.com>
 <E77A15DB-49C6-40CC-ACB1-D577CA4E65FE@newclarity.net>
 <CABdc3WpPRx=znZsqG1uy97wehW1Q9J_Goo7mkp8x6oDyWDSbZw@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] Object Initializer
From: mike@newclarity.net (Mike Schinkel)

--Apple-Mail=_C58FABE4-A770-4189-9B1D-F1EDCBE7CA6F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

> On Sep 13, 2019, at 2:39 AM, Micha=C5=82 Brzuchalski =
<michal.brzuchalski@gmail.com> wrote:
> $obj->foo =3D> 123;
> Simply, that's not the way you initialize object property values.

So by the same logic this should be PHP's way to initialize array =
elements, right?

$arr['foo'] =3D> 123;

But it is not. Obviously we both know that this is the correct syntax:

$arr['foo'] =3D 123;

So that is why I think it would be more consistent in PHP for object =
initializers to use "=3D>" instead of "=3D."

But, I myself will not belabor the point beyond this message. Either =
others will agree with you or they will suggest to change to "=3D>" too.

> { $foo =3D 123 }; // unexpected "}" cause of missing ";"
> $bar =3D { $foo =3D 123 }; // unexpected "{" cause it's not allowed in =
this context
> Both examples are syntax error.
> You can use {} for separating blocks of code, but now if you wanna =
assign value.
> Everything considered syntax error can be used for feature shaping.

Hmm.=20

Ok, I will let Arnold reply to you on this if he feels that your reply =
did not address his concerns.

-Mike=

--Apple-Mail=_C58FABE4-A770-4189-9B1D-F1EDCBE7CA6F--