Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:111624
To: Andreas Leathley <a.leathley@gmx.net>,
 Benjamin Eberlei <kontakt@beberlei.de>, Derick Rethans <derick@php.net>
Cc: PHP Developers Mailing List <internals@lists.php.net>
References: <alpine.DEB.2.23.453.2008041440380.7489@singlemalt.home.derickrethans.nl>
 <CAEPJduk12mo-eizR=K7G9TdaMdk7=C5iq88QWwQ6B_tk02r=2w@mail.gmail.com>
 <CAEPJdumb5KmS04-qnGLfHf4mdbSbXcBf_1+67JvWcyyuJDtHZg@mail.gmail.com>
 <642e48c2-eccc-19d8-99fd-888062a6232e@gmx.net>
Message-ID: <a42bd956-9ecb-f814-5386-826e7121db48@beccati.com>
Date: Wed, 19 Aug 2020 11:08:59 +0200
MIME-Version: 1.0
In-Reply-To: <642e48c2-eccc-19d8-99fd-888062a6232e@gmx.net>
Content-Type: text/plain; charset=utf-8
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Shorter Attribute Syntax Change RFC 0.2
From: php@beccati.com (Matteo Beccati)

Hi Andreas,

On 19/08/2020 11:01, Andreas Leathley wrote:
> I mentioned the benefits of @{} in an email to this list on Monday, with
> the proposal to have both @@ and @{} as attribute syntax, so both camps
> could have their syntax (one with delimiters, one without) with minimal

Please, one and only syntax would be plenty. We have history showing
that having two was not a brilliant idea, i.e. string offsets.


> But I guess the division about syntax is too big at this point to
> consider an approach where we just offer both types of syntax. From a
> PHP developer viewpoint, it would be preferable though.

To each their own. From my viewpoint, and possibly quite a few other's,
having two syntaxes is not preferable.


Cheers
-- 
Matteo Beccati

Development & Consulting - http://www.beccati.com/