Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:107068 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 67723 invoked from network); 13 Sep 2019 11:53:09 -0000 Received: from unknown (HELO php-smtp3.php.net) (208.43.231.12) by pb1.pair.com with SMTP; 13 Sep 2019 11:53:09 -0000 Received: from php-smtp3.php.net (localhost [127.0.0.1]) by php-smtp3.php.net (Postfix) with ESMTP id 8059E2C1342 for ; Fri, 13 Sep 2019 02:29:15 -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=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,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-pl1-x62b.google.com (mail-pl1-x62b.google.com [IPv6:2607:f8b0:4864:20::62b]) (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:29:14 -0700 (PDT) Received: by mail-pl1-x62b.google.com with SMTP id w10so1899353plq.5 for ; Fri, 13 Sep 2019 02:29:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=newclarity-net.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=6uukDefYJjHx/rSEiVEhUxxGXNcOrIFy0gh+vHhsFqM=; b=wpCn8b/3hjO14mxL1SuuTvY5Xg1tEJalJjZEX9jAEdI3i3xduSIIyvnD9SBIDzVVeQ xS8Nz/E6fh8/ipovmUq5xw6F/jWoFJqGpWa7iM54wT9QrPrWCo4lREH53qevjzdquE0o Li1d9WFst3jPIQhPajCnpPhoBjtWgslClQIYc20iKeQOf8PHwtx7YrNpHxl+uE2CHv1M aJ+4ab2sWlOy2Iwj151jdkl3mtjgbr0t8VxRDPwClZ46342SZgYKDqcDKLpUfD+1kKZ4 SknQ8nS4ZFV81ilS9QG/0fWU+q8zUGzdeRRoCSpiULbFSMdHMyY9W6KZUUO/Bvts2nFW uH3g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=6uukDefYJjHx/rSEiVEhUxxGXNcOrIFy0gh+vHhsFqM=; b=h/9NjlfoZtr0siCfRnOoy2crZB2fnCmNuWcyltqUxrXojvqHm4sJWLz92HSMn+eN/z 1UdGEiVTGFlkm+UYAIh5X9oTA+Ef+wH6ckPKfPCF7+Lp+A5Oc6ZldRO92OZscVILBGAp bMTWBlTAeSXIYKn4N8wjsUnaHUMnOCRaNTQhF7+b+p9Mj4+oy5FKc1YoEZKL5Ica6fzd DtB+yG+cGbA/m5KviyTNs0XPyrrP4hDpbUFvDLZyUENq60U0NepI9zXLEODz50TbAKwF 24IZ6Oipkqh8cZVs2FcYPTauuHAqqy2EBIyxZcqOz1uJ4lyz1SP9ZKObQPGBMpuGzo0/ kUzg== X-Gm-Message-State: APjAAAXuVHA8ZCtN++ZsdabNwNGRNx/XO9FFel8Ww6CEKeuwT3rKWScC AJBA1XgBwGqFep/IHHP/6JsRWA== X-Google-Smtp-Source: APXvYqxDwJmBUcHd/c8b/+FueZYywaoiDaWENI8TlZQvxG8JypqxC/UTx7Q2zZF/MuP+EXx7nKKXmw== X-Received: by 2002:a17:902:7c13:: with SMTP id x19mr49354564pll.322.1568366954092; Fri, 13 Sep 2019 02:29:14 -0700 (PDT) Received: from [192.168.202.38] (50-252-183-45-static.hfc.comcastbusiness.net. [50.252.183.45]) by smtp.gmail.com with ESMTPSA id t12sm29456857pfe.58.2019.09.13.02.29.13 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 13 Sep 2019 02:29:13 -0700 (PDT) Message-ID: Content-Type: multipart/alternative; boundary="Apple-Mail=_C419D311-95E2-43DC-B357-41F9B5BDBBB0" Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Date: Fri, 13 Sep 2019 02:29:12 -0700 In-Reply-To: Cc: Arnold Daniels , PHP Internals To: =?utf-8?Q?Micha=C5=82_Brzuchalski?= References: <74C03BB1-28DF-4694-A91D-2516C545F8B2@gmail.com> <3CA484B0-BCA3-4A2B-B2A6-8B845F9C462B@newclarity.net> <2CA1F9C5-AC54-4E45-AE9E-20BB32BD7093@newclarity.net> X-Mailer: Apple Mail (2.3445.104.11) X-Envelope-From: Subject: Re: [PHP-DEV] [RFC] Object Initializer From: mike@newclarity.net (Mike Schinkel) --Apple-Mail=_C419D311-95E2-43DC-B357-41F9B5BDBBB0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > IMO should stay specific for arrays only. Why? Is there an objective reason? =20 Is there some aspect of the syntax that makes it appropriate for arrays = but inappropriate for object initialization?=20 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 = it seems very appropriate to use for object initialization too. That said,=20 1. I don't feel strongly about iti either way,=20 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 } #fwiw -Mike= --Apple-Mail=_C419D311-95E2-43DC-B357-41F9B5BDBBB0--