Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:119321 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 77074 invoked from network); 18 Jan 2023 16:34:09 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 18 Jan 2023 16:34:09 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 41160180551 for ; Wed, 18 Jan 2023 08:34:08 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-0.2 required=5.0 tests=BAYES_40,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM, 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-wm1-f44.google.com (mail-wm1-f44.google.com [209.85.128.44]) (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 ; Wed, 18 Jan 2023 08:34:07 -0800 (PST) Received: by mail-wm1-f44.google.com with SMTP id e19-20020a05600c439300b003db1cac0c1fso311613wmn.5 for ; Wed, 18 Jan 2023 08:34:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:mime-version:message-id:references :in-reply-to:user-agent:subject:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=ECXfHohTg6DhpDqFFQ7caeR3uUmpLgZ0IVSO3PpmLm8=; b=SJMt6DOdwZsEAH+MBL+xWhOU/zmlW2QRfdjgPYukchVyRH7C0dJGH2x+9UBTmhiSiH dN3aJWsjTDS+bLI4chBoLg3FHyXPEhvPSuNn3auz5UARVeawAh52DMNDv5Txx8yo85P+ mXMF67ME1jvduQxqRiXyFu5I8n8MflxRewyT6leDh5nT3/WAgmy6IqpzW67wXmX0lYeR ei7xKcHWlgw4M6AMoK9OpbeMqbLDNd1EKk40TMZalOej5p7YS4RQu9bJelmaL1vKIzBi K0EFk2b4xde33a+QckjxaOzFxq8rkAg/DQRie8aTPNLdEXBix0Wu/ieOfpwDx6uk19n1 TN2w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:message-id:references :in-reply-to:user-agent:subject:to:from:date:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=ECXfHohTg6DhpDqFFQ7caeR3uUmpLgZ0IVSO3PpmLm8=; b=CmJAnrbpTFO+jidPKKjsPNzL7rN34q4ndHs8bi7f1KiDhnnLq7O7RPkgdpXGPAy1Mv 1bV4plexRf9j+1gdwVS+nQLuDLCN437ssUDq2Syi+jolYUdszVpefaoY0FI81kp/67gZ MBWR+b5YTX3AQ8hPxybo92PDagjGTlZ0v/2lxF7WPqjnwsySruoscjA9M9XXM0V6pYUN JGvvkHETK+WFRi+bidjD2IIjELecz5AULPBXNTpxuxb5d0iMcwiPez4lWAtHdraonp1M +le6+oHkD6++SS1C+dZbpRUItrzG65iFqECt9xU7yP+GujD3iL4M/2fFTHQYvgqN5ypS OlEw== X-Gm-Message-State: AFqh2kpWHNynH4DgksyTMFZnDURYbX51twTVxh9IHM98lKnIyxjZ824W Z6eAtqNcJF+2V/XlmCU34LuxRO0hWfg= X-Google-Smtp-Source: AMrXdXvFxvCV1c3773cAaEKbzGtjUPLChZt4sxTdjgLUb7rSALGRCNJBIeYCk8kakJkiL2sgWyUDJA== X-Received: by 2002:a05:600c:3d06:b0:3da:f945:2354 with SMTP id bh6-20020a05600c3d0600b003daf9452354mr7253648wmb.41.1674059646576; Wed, 18 Jan 2023 08:34:06 -0800 (PST) Received: from [127.0.0.1] (cpc104104-brig22-2-0-cust548.3-3.cable.virginm.net. [82.10.58.37]) by smtp.gmail.com with ESMTPSA id m31-20020a05600c3b1f00b003db0cab0844sm2768939wms.40.2023.01.18.08.34.05 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 18 Jan 2023 08:34:05 -0800 (PST) Date: Wed, 18 Jan 2023 16:34:04 +0000 To: internals@lists.php.net User-Agent: K-9 Mail for Android In-Reply-To: References: Message-ID: <04288995-54CE-41A4-BFFD-A7CF72F16D3F@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] [RFC] Path to Saner Increment/Decrement operators From: rowan.collins@gmail.com (Rowan Tommins) On 18 January 2023 15:32:28 GMT, Derick Rethans wrote: >> The goal of this RFC is to reduce language complexity by making $v++=20 >> behave like $v +=3D 1 and $v-- behave like $v -=3D 1; > >If that is the goal, then I would agree with this RFC=2E > >However, changing the PERL string increment feature does not IMO fit=20 >into that goal I agree, *changing* its behaviour does not achieve that goal; only removin= g the behaviour (with an appropriate deprecation period and upgrade path) a= chieves the goal=2E (For completeness, the only other way to achieve the goal would be to add = support for string increments to the +=3D operator, and presumably also the= + operator to avoid a different inconsistency=2E That is, make 'a' + 5 =3D= =3D=3D 'f'=2E I don't think that's even worth considering, but it's the onl= y other way to achieve consistency=2E) Regards, --=20 Rowan Tommins [IMSoP]