Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:119290 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 55960 invoked from network); 17 Jan 2023 14:28:40 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 17 Jan 2023 14:28:40 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 187631804A9 for ; Tue, 17 Jan 2023 06:28:40 -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_20,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,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-pf1-f173.google.com (mail-pf1-f173.google.com [209.85.210.173]) (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 ; Tue, 17 Jan 2023 06:28:39 -0800 (PST) Received: by mail-pf1-f173.google.com with SMTP id i65so20124351pfc.0 for ; Tue, 17 Jan 2023 06:28:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=wrCqJbuHM1O02q0CXdeuE6bJOKsA+WOG2A5icoeq27w=; b=F6aJpg/KUSnKJVQqYDZ0zX/KD1jKvjo+5nGOhuIhaAASUHP82kiGrrQhO0oDKTgl9F zc7V9ouefZhYbk0T5rFpq626FdNm32OxLF6mfuenlEIXPaEh2XYJn0sjlCv2RdBaLmye rK8RpNDtmrTW8E0kS4NVzPMv1wXERV1rGwiy3ZbKWEeco8qK8hKcUdpz3v2dwZ/iqCs6 sQ5PSdYmQ7PO2tLb63hlWXV4zq95bQ2ZqgUp2kSl5kMogIJ2Gu7yink3jhwIRV4LLOYd R10C1mk7Ut6ohzXY1ThR9rCvsY0xqu4iAOkpdZ2bTZSmVE8RCzMoCn6UbyOOjMsg2fck 1k3Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=wrCqJbuHM1O02q0CXdeuE6bJOKsA+WOG2A5icoeq27w=; b=gLSDdW8SJr6+yUrj3CsTKdDBAQB2X9/o58dSfVPTcy0FOLjHRdmvuBV6OHmuvtEjOb HrErMQtIRXU9Fw3RW5UXI2ve0xd71XeIAxj2svbZeR46JR28roNP/hFm5TL8JHTmJ1CF p2iw5SAX0aJJEivmw6xkus2eMTkCqp1wSc3ppensygQZ+KaB3Mk5WrAbyy+G/lItWCz5 IKca5DcPDAi2kUp4GCiuGgJcgVR4T2aYF+ZFlsuvMMhpM+ZJPwaG90qdEky1M40NyW6/ 9YBqyfLBXIvvHcLDpezgXsV5diNuSAZH7VUAbRJ98iG/JQbBWlpkKk2MZQkWrmB8W0h6 DluA== X-Gm-Message-State: AFqh2kr5JLpkpJVg70Mw4VFgaw+tvvnoto5wIrLWFczhUj2Mwz1uLOMo NCQeV3IehkTLkPcnB///znKwCbvdsXddsaneRncqiXPRw2E= X-Google-Smtp-Source: AMrXdXv/XBm78BI5cJ1MCnrEwTqWazGyla1xW20aQcAnhaqHT8kCGmyfMmARA6118vCbZ1j1Toa1gVbLsVkW2do9AgY= X-Received: by 2002:a63:2786:0:b0:492:50dc:da4e with SMTP id n128-20020a632786000000b0049250dcda4emr161745pgn.462.1673965717508; Tue, 17 Jan 2023 06:28:37 -0800 (PST) MIME-Version: 1.0 Date: Tue, 17 Jan 2023 14:28:26 +0000 Message-ID: To: PHP internals Content-Type: multipart/alternative; boundary="000000000000f5573005f27683fc" Subject: [PHP-DEV] [RFC] Path to Saner Increment/Decrement operators From: george.banyard@gmail.com ("G. P. B.") --000000000000f5573005f27683fc Content-Type: text/plain; charset="UTF-8" Hello Internals, I would like to start the discussion on the Path to Saner Increment/Decrement operators RFC: https://wiki.php.net/rfc/saner-inc-dec-operators The goal of this RFC is to reduce language complexity by making $v++ behave like $v += 1 and $v-- behave like $v -= 1; I am expecting the contentious part of the proposal to be the deprecation of the PERL string increment feature to achieve the aforementioned goal. However, I believe the benefits of aligning the behaviour of the increment/decrement operators with addition/subtraction are larger than keeping support for the PERL increment, which in its current state has various shortcomings. Best regards, George P. Banyard --000000000000f5573005f27683fc--