Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:107150 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 84779 invoked from network); 16 Sep 2019 10:54:20 -0000 Received: from unknown (HELO php-smtp3.php.net) (208.43.231.12) by pb1.pair.com with SMTP; 16 Sep 2019 10:54:20 -0000 Received: from php-smtp3.php.net (localhost [127.0.0.1]) by php-smtp3.php.net (Postfix) with ESMTP id EF3E42CBF5F for ; Mon, 16 Sep 2019 01:31:11 -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,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-yw1-xc42.google.com (mail-yw1-xc42.google.com [IPv6:2607:f8b0:4864:20::c42]) (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 ; Mon, 16 Sep 2019 01:31:11 -0700 (PDT) Received: by mail-yw1-xc42.google.com with SMTP id u65so6963790ywe.4 for ; Mon, 16 Sep 2019 01:31:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=newclarity-net.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=A7V8qPoIg1W4Os7ON0+Mf4/hhG4gOSnoEqHEUQBm1fg=; b=PIZZuud8bCQqEGIAxQz9x8gaOrHRIbBv/iUBu+KGjPvsIjsu6TkY6Arsaakk5jPPyp JSWhfEQote/ZdM+hjzIPeTnpfMIjSbFZfIJqNGlSLKXxHmss95j38Ynizj5AKtw42Zij cY2+/VqYZTXkcZGlCJ/S+fiMxGKlpthufUp+RSDWAtOtCPn4OMKcgd7Cz+Z4Q47ZnacA dnJJOBlIK9FKTbsnHwKIxAMBh3tcpnNEG4/SoNDbQcOVRMh12QcTNN5S9kFeJI/RuFEh DJ4BM24oaVRrmEWKsq1R7XibJ5yXD8Y2FdpBIFC7vmhFxbvSj1bVds6lrS/Cb7Wn771X y2Rw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=A7V8qPoIg1W4Os7ON0+Mf4/hhG4gOSnoEqHEUQBm1fg=; b=iVsOyEGPNEfOc0dQgzz6FSfCRoPK0zH2Kqa0mOqAsTd0fEmuzLhGqw/H2RRmtWfMqU d0K9KPBbnHcg+YsjuZ0aeF2w4CGd7XNXw38IZ/aqzsn57g2KXMh4OA0iSnqXWKSbrXy9 PNf1mK5c5Pj9lMJUxerEXAnMhCLKTAyWgbFiIUyOFFobVbQPOUVeiC3VEVnRJR7Mv5eZ 770XpOPxtZ/6AN1vX/8sZ10zIwF6wlyQkxLhQacLzhA0HMFGh72n9pdk2ZeYvSb9vqSa 8UXig38ZS89en88Snkvi5I3OQSDstj9JbggusDDXECxtOK7akxlTxXjEowfl7hV10qfj gu3A== X-Gm-Message-State: APjAAAXpypCUaH0rc6eWl32I5BYtO57BvotFPJ1IsTOC2fmUGdKclP80 8CL7db0xtJO5pK3k68ZXamL6Dg== X-Google-Smtp-Source: APXvYqxwQFaxCeyU0niJGGovAoWyUHXsSkfLCkT5AS2lvTFib6Cn1tJkZtvF7bRt+ExVoyLH6tsLpA== X-Received: by 2002:a81:6e03:: with SMTP id j3mr45177045ywc.297.1568622670972; Mon, 16 Sep 2019 01:31:10 -0700 (PDT) Received: from ?IPv6:2601:c0:c67f:e34e:f4e5:82c9:8e75:5377? ([2601:c0:c67f:e34e:f4e5:82c9:8e75:5377]) by smtp.gmail.com with ESMTPSA id t186sm6046581ywd.54.2019.09.16.01.31.10 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 16 Sep 2019 01:31:10 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) X-Priority: 3 In-Reply-To: Date: Mon, 16 Sep 2019 04:31:09 -0400 Cc: internals@lists.php.net Content-Transfer-Encoding: quoted-printable Message-ID: <340E0F88-72CF-40AA-B8B0-E68AC3A72942@newclarity.net> References: <572E7B74-9D56-483F-94A6-F2955C63AA56@gmail.com> To: Arnold Daniels X-Mailer: Apple Mail (2.3445.104.11) X-Envelope-From: Subject: Re: [PHP-DEV] The RFC discussion process? From: mike@newclarity.net (Mike Schinkel) > On Sep 16, 2019, at 4:10 AM, Arnold Daniels = wrote: >=20 > [Arnold Daniels - Chat @ = Spike](https://www.spikenow.com/?ref=3Dspike-organic-signature&_ts=3D5wb22= ) [5wb22] >=20 > On September 16, 2019 at 7:40 GMT, Mike Schinkel = wrote: >=20 >>>=20 >>> 1. Alternatives to the RFC? >>> 2. Enhancements to the RFC? >>> 3. Modifications to the RFC? >>> 4. Other features that are a pre-requisite for the RFC's feature? >>> 5. Other features that would add value to the RFC's feature? >>>=20 >>>=20 >> Everything you list is appropriate to talk about as feedback to an = RFC. >=20 > IMHO what you see with the object initializer discussion, has gone = beyond "I think named arguments is a good alternative, because ...". A = big part of the thread is about how to best implement named arguments = and other (possibly alternative) features. This overshadows the topic of = the original RFC. >=20 > Additionally, even if the general consensus is that named arguments = are indeed a better alternative, it doesn't help to advance PHP forward, = since no progress is being made to implement that feature. >=20 > As such, it would be preferable if the RFC about named arguments = (https://wiki.php.net/rfc/simplified_named_params) was revived and = discussed out of context of the object initializer RFC. To clarify again, I had these questions *before* the Object Initializer = RFC was proposed. Please do not assume I asked these questions because of any form of = "sour grapes" about the Object Initializer RFC discussions. Yes I want = object initializers but my questions were not a passive-agreesive way to = try and get that to pass. They are honest questions unrelated to the = Object Initializer RFC that I have wondered about based upon my reading = of all the discussion on the recent contentious RFCs. I created a new thread so that my questions could be discussed in the = general context and not in the context of Object Initializer RFC. The = only reason I referenced the Object Initializer RFC because it was a = recent example and thus a convenient one to reference. I now wish I had = not included any examples in my list of questions because it has caused = the answers to be focused on that RFC and not RFCs in general. -Mike