Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:107070
MIME-Version: 1.0
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>
In-Reply-To: <E77A15DB-49C6-40CC-ACB1-D577CA4E65FE@newclarity.net>
Date: Fri, 13 Sep 2019 11:39:25 +0200
Message-ID: <CABdc3WpPRx=znZsqG1uy97wehW1Q9J_Goo7mkp8x6oDyWDSbZw@mail.gmail.com>
To: Mike Schinkel <mike@newclarity.net>
Cc: Arnold Daniels <arnold.adaniels.nl@gmail.com>, PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000053607505926c0894"
Subject: Re: [PHP-DEV] [RFC] Object Initializer
From: michal.brzuchalski@gmail.com (=?UTF-8?Q?Micha=C5=82_Brzuchalski?=)

--00000000000053607505926c0894
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

pt., 13 wrz 2019 o 11:29 Mike Schinkel <mike@newclarity.net> napisa=C5=82(a=
):

> IMO should stay specific for arrays only.
>
>
> Why?  Is there an objective reason?
>
>
$obj->foo =3D> 123;
Simply, that's not the way you initialize object property values.

When you use "=3D>" in array context you're pushing a new value to array an=
d
it'll work without labelling it with key
where the key could be number index or string index in what shape you want
(whitespaces etc.).


> Is there some aspect of the syntax that makes it appropriate for arrays
> but inappropriate for object initialization?
>
>
>  These are honest question.
>
>
> My two cents: I would like to type less too, but I have always assumed
> that "=3D>" was the PHP-ish syntax for initialization of a structure so i=
t
> seems very appropriate to use for object initialization too.
>
>
> That said,
>
>
> 1. I don't feel strongly about iti either way,
>
> 2. Unless using "=3D>" would make naked object initialization possible =
=E2=80=94
> i.e. { foo =3D> 10 } =E2=80=94 given that it seems, as Arnold said, this =
would
> conflict with other meanings: { foo =3D 10 }
>
>
>
{ $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.

Regards,
Micha=C5=82 Brzuchalski

--00000000000053607505926c0894--