Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:107067 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 65475 invoked from network); 13 Sep 2019 11:46:54 -0000 Received: from unknown (HELO php-smtp3.php.net) (208.43.231.12) by pb1.pair.com with SMTP; 13 Sep 2019 11:46:54 -0000 Received: from php-smtp3.php.net (localhost [127.0.0.1]) by php-smtp3.php.net (Postfix) with ESMTP id BD3AF2D2025 for ; Fri, 13 Sep 2019 02:23:00 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp3.php.net X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS3215 2.6.0.0/16 X-Spam-Virus: No Received: from mail-ot1-x32d.google.com (mail-ot1-x32d.google.com [IPv6:2607:f8b0:4864:20::32d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by php-smtp3.php.net (Postfix) with ESMTPS for ; Fri, 13 Sep 2019 02:23:00 -0700 (PDT) Received: by mail-ot1-x32d.google.com with SMTP id 67so28789171oto.3 for ; Fri, 13 Sep 2019 02:23:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=pRylNEXELCEcWeit4WHRoUHvCR0cnrgu3ap6YSXQyhY=; b=CB/gc6lveWoMgD4GcvHYPtdFuaF66mkVS0SfcXu9lZ0jkuqoTRynczHhOzr3oCv6pm +vF/0zmbErEKfmUeJ5cLsILoWJeqL3DsOjY8kXgLNVCLF9KoR+HcyKaqd3NNsCzRFPf5 QEg5OizH1xnKYqbNCr+SikNaknj/4dYNYu4fH8kxSW+aiBQ/ELx4vD9LZdmqbJGpP6l6 OAYpLao2vrAyDOLbsLY8nGn9UpLDheD3k1AGScxBxk2NeugTJqjdjl6wVofEdn54V9rY e86JYJ+N2XvhIcnoGrVuVspVGOgE9xbxURQZYPvzVhazz6S4EG/IhySOkYDpRYukb3eb KfLQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=pRylNEXELCEcWeit4WHRoUHvCR0cnrgu3ap6YSXQyhY=; b=uYNIdG3hCe50YqQS5WtCFLq++keexEKXh2WMai2uuT7oNGZXkwL46oIjQWZIGBPkQt oVP5cfMeAnKehFaxtUAY/f1XrZHXRjSSXY+jlnA1iUuCiw005vxbKoPqWGRxqo5kFglO 5wzean32FIWH1hnQEn4EIp9D7slbXo+NDHDp+19Clg8NMfSquxi5+TWHUNMB19jJmPO6 xzNEX+POQLHy3naE9ykWZQx6eHFMPa2FwI9ZffACKaKn0/SwU1QVyDlsvStGVXNJRRtl HdS3jDRC4zOXrFDxp0AjR101hv0KUjCinjlhcdOHwKirdFr0xOzuO+GOL3D3X9GWWpvt /Fyw== X-Gm-Message-State: APjAAAWyonDe/eL44ju1ZYaP4a7dUzI0xY4GVgKAdN/04rZnP16Ho2UB DBxmNgjasgJPsMMDvqYV8J5Z8CAVmeWORejSnSw= X-Google-Smtp-Source: APXvYqw5NTJ0Spq7KE3xt4vijiiFAcsED01wBQ8OF3OUA3VFqCpWKpDWaCFRV81YpOW10v2svs4UZ9LfmDCsqpcwPcQ= X-Received: by 2002:a05:6830:128b:: with SMTP id z11mr2049430otp.79.1568366579482; Fri, 13 Sep 2019 02:22:59 -0700 (PDT) MIME-Version: 1.0 References: <74C03BB1-28DF-4694-A91D-2516C545F8B2@gmail.com> <3CA484B0-BCA3-4A2B-B2A6-8B845F9C462B@newclarity.net> <2CA1F9C5-AC54-4E45-AE9E-20BB32BD7093@newclarity.net> In-Reply-To: <2CA1F9C5-AC54-4E45-AE9E-20BB32BD7093@newclarity.net> Date: Fri, 13 Sep 2019 11:22:48 +0200 Message-ID: To: Mike Schinkel Cc: Arnold Daniels , PHP Internals Content-Type: multipart/alternative; boundary="000000000000d903dc05926bccf9" X-Envelope-From: Subject: Re: [PHP-DEV] [RFC] Object Initializer From: michal.brzuchalski@gmail.com (=?UTF-8?Q?Micha=C5=82_Brzuchalski?=) --000000000000d903dc05926bccf9 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Mike, I am curious why your RFC uses "=3D" instead of "=3D>" for separating > properties from values? > > If we used "=3D>" it is potential =E2=80=94 with lookahead parsing =E2=80= =94 that the > following could be unambiguous: > > { foo =3D> 10 } > > The reason about choosing "=3D" was a simplification of instantiation and properties initialisation and we use "=3D" to assign property values now. The "=3D>" is specific for array key pairs and IMO should stay specific for arrays only. Thanks, Micha=C5=82 Brzuchalski --000000000000d903dc05926bccf9--