Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:124842 X-Original-To: internals@lists.php.net Delivered-To: internals@lists.php.net Received: from php-smtp4.php.net (php-smtp4.php.net [45.112.84.5]) by qa.php.net (Postfix) with ESMTPS id 256EF1A00B7 for ; Sat, 10 Aug 2024 23:18:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=php.net; s=mail; t=1723332030; bh=f1/T07OE+67OUJHKYwFxQGVKd2EkyUh0jFstfm0G1iI=; h=Date:To:From:Cc:Subject:In-Reply-To:References:From; b=a6hSlNFqYEfgsqLniV9vwirY3iSfmyiHDET8j4GlamNmnMvNr2DscyVXl+3rEg2nl 2YaR8Krtb1Jwt7MRQg4LQA+11l9xt4wxHvSzaPzvL/dhfGJt1EgjgV4C7+GKvU1993 aIJFY9A0wp2Qp45abhEGk4PGacGa8vJb4IeFCiJiOnw4qVD6j+fYV2y/l6H3piRuYJ u5cOjU+XOSMefOjnSGoZh5sHafWxWn28xAVDDjQ3j1qI4RGdFqhv1QTlZEh53Wbc9R IGIJ6nKyREqAy3kuL1svHOZmgnUncLK/g6KN0MuqfkndQAGhsV9vyT+cVU4A3s4bod Kl/iRQUb6nlvA== Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 28B9E180072 for ; Sat, 10 Aug 2024 23:20:29 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=0.6 required=5.0 tests=BAYES_50,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,DMARC_PASS,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H4,RCVD_IN_MSPIKE_WL,SPF_HELO_PASS,SPF_PASS autolearn=no autolearn_force=no version=4.0.0 X-Spam-Virus: No X-Envelope-From: Received: from mail-4317.proton.ch (mail-4317.proton.ch [185.70.43.17]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Sat, 10 Aug 2024 23:20:28 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gpb.moe; s=protonmail2; t=1723331922; x=1723591122; bh=f1/T07OE+67OUJHKYwFxQGVKd2EkyUh0jFstfm0G1iI=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=DYLlEEhH0P270M/sf76WO+CZl1N5wevjtOezryUpSqYx1P5OK3otcFWUFeTF++zkF QV6wFghz0MxH5WNKoFuSPxp7A5rlnm4mM4ZMUTvVckARsiRIfraxCs5zp2XWBii/mz EhN6ejn+L6p0ckPYw1XATadwnXU1sRWS3hY+vNU7iUCB4cWVH3S216cH53uvGExAgb 6wV4QQJnE3YDomo4MN0IWyXPBsk8HOVVCLJ/XpN4EgT83o6zbisVxaQD4oZ527QQxO Etvg54+FFOrAuhXFQSh921Sx17FYZ5M5ltxhAv4ac4m3gzeD1LfKuMgE2sbmZaPmf7 WdoYcjalJL1Gg== Date: Sat, 10 Aug 2024 23:18:37 +0000 To: Larry Garfield Cc: php internals Subject: Re: [PHP-DEV] [RFC] [VOTE] Transform exit() from a language construct into a standard function Message-ID: In-Reply-To: <6decd4f6-e504-47e2-831b-ad5a3bbcf462@app.fastmail.com> References: <0FA837CD-60C3-4F4C-9044-C44FB0AF5788@php.net> <32BE9C65-F955-44F0-B994-D588D851902E@heigl.org> <1f1cda9b-a159-4f92-90b0-2ca7a3cec262@heigl.org> <6decd4f6-e504-47e2-831b-ad5a3bbcf462@app.fastmail.com> Feedback-ID: 96993444:user:proton X-Pm-Message-ID: 49e43442b00f780c49b794fd31b1f0815969a4c9 Precedence: bulk list-help: list-post: List-Id: internals.lists.php.net x-ms-reactions: disallow MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable From: internals@gpb.moe ("Gina P. Banyard") On Friday, 9 August 2024 at 16:03, Larry Garfield = wrote: > How exactly would voters veto an implementation if not through the RFC? T= hat's literally the only formal input mechanism they have, and previous att= empts to add others have been soundly rejected. >=20 > As a historical note, the partial function application RFC was declined d= espite there being general consensus that the proposal was quite good and q= uite desireable. The issue was that Nikita felt the implementation proposed= with it was too fragile, and wasn't sure how to make it less fragile, so h= e voted No and several others followed suit. I am fairly confident that if = a less-fragile implementation could be found, it would pass handily. >=20 > So yes, RFCs have been rejected in the past on "implementation only." The implementation for the attribute syntax using @[] (before it got revote= d) would have been vetoed due to implementation issues if the "Treat namesp= aced names as single token" RFC wouldn't have been accepted. I am very much aware that RFCs have been rejected on implementation, but ev= en if an RFC is accepted it can be vetoed by core developers. And once again, I still do not have any idea why Derick has issues adding s= upport to XDebug. Especially as Tim seemingly managed to do this while being unfamiliar with = the codebase. Best regards, Gina P. Banyard