Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:118012 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 13304 invoked from network); 20 Jun 2022 12:55:43 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 20 Jun 2022 12:55:43 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id DAB9418054F for ; Mon, 20 Jun 2022 07:44:44 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,FREEMAIL_REPLY, HTML_MESSAGE,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-ed1-f52.google.com (mail-ed1-f52.google.com [209.85.208.52]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Mon, 20 Jun 2022 07:44:44 -0700 (PDT) Received: by mail-ed1-f52.google.com with SMTP id e40so2894000eda.2 for ; Mon, 20 Jun 2022 07:44:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=6uOxGr4R1kp7/7ly57AIotSdBmZtDmlcM93W1P3R75Q=; b=Xx8xWp0tU3wtJ9MqBnCBltHK6Xh8qdWX6pgo1+uTkx3TbOxUW0k1+kjGzGYqxEnPg9 /OcOoZrPeMPRXW5sRr8UqeLlgFGImljvYDoFwampA9wm5/vshU41NBYDw3rxzQdf6gdl aGLxPIPU06qxrSZ+3lkF/r52WHQm9w2RSo9Uq3IzBHKVRidON/jnLzlT9sXJ/sBSHQ/2 HzBNMEpFOkPnnZ5s/16stD9EJGh+sYWQ25aQSnKtZ0noFA3oL++Xz6jyXUjufRUusbSU 6VIV7PTGiMvWfFpH4V4I6alnqXmUHYeq80WlydsojTCvipqn8mC68I4tbEuko8eUH3jU dHrg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=6uOxGr4R1kp7/7ly57AIotSdBmZtDmlcM93W1P3R75Q=; b=fLRt3qHDOYFqcdbDwJo9MXo4VwmF+ar+oNxU7jb7q4ysqMQT+u8hQhqVpZX7qeuMJn uj1wjsQ3DSog45e3K2Oaz1bYUrUxjRBEwP2TBtrAcC/vYwReCZg+XCZiBIn2NSL1jRZ5 o5huEjgiJkUH5loCuawi72VXH0lUtmJC6BNYquzTRmodfqziTtgXzzgW62WNbLpTpk1w 5hJp6qLAzVUvbXsTrNL9StezJx2mM1KHpSzr5hGy7jbpxd6AIpq9WGH4oXTrSSCGhv6b FHNBRfROlAZuy4kTOnCCQQsLaiAznTcLg5ABYMuPamkkrZ0r/dCqh4JxPnRfbhOOt/cx 7NSw== X-Gm-Message-State: AJIora8KuTyphPiNKRXou/irXtJgU1sAExZQLtRwx0JhfMCd1N/Zr7Jd m09XrLCseZ/QgBpX60BAgiXOpNGgaZ9UaKBi2x0= X-Google-Smtp-Source: AGRyM1sPQL4LKmsYWiLG/fjB5u1OU+/IO0/F6AVa+rToL4mquUsDMtw78NgpVVbuTvdhkODKbKzkUccA3tzictBv9ng= X-Received: by 2002:a05:6402:448a:b0:435:3fbe:2593 with SMTP id er10-20020a056402448a00b004353fbe2593mr26473928edb.226.1655736283139; Mon, 20 Jun 2022 07:44:43 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Mon, 20 Jun 2022 23:44:28 +0900 Message-ID: To: Lynn , PHP internals Content-Type: multipart/alternative; boundary="000000000000ff908205e1e2246a" Subject: Re: [PHP-DEV] [RFC] [Under Discussion] Random Extension Improvement From: zeriyoshi@gmail.com (Go Kudo) --000000000000ff908205e1e2246a Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 2022=E5=B9=B46=E6=9C=8820=E6=97=A5(=E6=9C=88) 23:37 Lynn = : > On Mon, Jun 20, 2022 at 3:15 PM Guilliam Xavier > > wrote: > > > Hi, > > > > > https://wiki.php.net/rfc/random_extension_improvement > > > > Thanks, but I am not sure about your argument in "Classnames are not > > canonicalized": does "PHP applies strict PascalCase to class names" > > (which remains to be proved) really imply to rename *acronyms* (e.g. > > "CombinedLCG" to "CombinedLcg")? especially given existing classes > > like "SimpleXMLElement" (not "SimpleXmlElement"), and that the > > accepted "Class Naming" RFC (https://wiki.php.net/rfc/class-naming) > > voted for "PascalCase except Acronyms" (not "Always PascalCase") -- > > excerpts: > > > > Not specifically directed at this discussion, but perhaps this needs a > revision. HTTPStatus is much harder to read for me than HttpStatus and it= 's > unclear where the boundary of an acronym starts or stops. If anyone ever > decides to make an RFC for this, you have my vote. These Acronyms are > treated as words and thus should follow the same naming convention. If th= ey > shouldn't be treated as words, write their full name: > HypertextTransferProtocolStatus. > I support "PascalCase except Acronyms" for readability, but would like to see this clarified as I get very lost when implementing new features. I think it is necessary because I expect various OO APIs will be added in the future, like cURL. But, I do not have the right to vote. :) --000000000000ff908205e1e2246a--