Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:119754 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 59170 invoked from network); 28 Mar 2023 12:57:45 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 28 Mar 2023 12:57:45 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 72771180544 for ; Tue, 28 Mar 2023 05:57: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=-2.1 required=5.0 tests=BAYES_00,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-pl1-f182.google.com (mail-pl1-f182.google.com [209.85.214.182]) (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, 28 Mar 2023 05:57:43 -0700 (PDT) Received: by mail-pl1-f182.google.com with SMTP id o2so11543302plg.4 for ; Tue, 28 Mar 2023 05:57:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1680008262; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=O5c6mquyYzelcT4Owv7WLOz7MaZGu+ZM8dECC5HLz60=; b=et1udDOFFUk4F8Iqu78JkhkXD+g3kYkcFP5E0S597kP9P6dbI+XujrXhFG/DpgHCS2 Exlc4s7YfLxIEhUeJJ2S7tejOjOwcOX75+dNM6dCrp3Pg1QWMuQ2Aiu/VomwhXsERGbN UTj46sFHhmhnGvfNxEbCkBsxgQOEnJ0eE2wjzQ8pJl7UsSazPU0Yf3MSLsp2tI09EZ0B HeO0tSxekHKkwUD1+omRx130QnrPLNyOcOvp9Xial3l0jorYjoCmgv2esxk/QFXhPI09 5oKzQWdylEbJhcfO/sgv+wBHs/MMl14TxEJrvr1ZmO5JBVca2rR5AidzkWzRYGAKGqtC KMsg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680008262; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=O5c6mquyYzelcT4Owv7WLOz7MaZGu+ZM8dECC5HLz60=; b=bDdB6y7RfFCEusJz8AebpIu4IVtwXOagXqA6TUQ/8Vx/vSi9p4MduDEimo17onPaTV gpz2RS0632aCjFX+nPnidQUdHss6kDNtibhwYYMNlys+FyDDlJFugu4CTaPaM206yJpU xw+yQ/3QrnHL9EnkrjUQfg7swUYH97s0RhCddF6QM1hlTc2PNigqMnH6rtahR16CPWdX VnDZCOMCi4Ruaoiz7QbKN9Hb1lmxQrQmsudcTFM6uVgqumegpkPWZo5hae36X7VCRVAY DuCErBiO+rbO8k+g44R0jwO9XcSkZP2tvY932cOIH8YCXgkewM9ZntvVD1qoBoJS1P+U HRDg== X-Gm-Message-State: AAQBX9ck7x6aAb3cvsAmPahSc0cy5GJrA1tfl20m3e6HefbxAUj6Uhhf PvvQcWDIUPtCwsRANTIyH5zMmPSjzb4gE8n84ys= X-Google-Smtp-Source: AKy350aScMIA7w2ZGVoaoboWl00jg/6yc3Cc1VKbxwfwMUIpEsZPhIDw6fpv1A/NxC2AinXI2LZuqNT/npUdw3/Q9ks= X-Received: by 2002:a17:902:b18a:b0:1a1:8f72:e9b with SMTP id s10-20020a170902b18a00b001a18f720e9bmr5507521plr.7.1680008262203; Tue, 28 Mar 2023 05:57:42 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Tue, 28 Mar 2023 13:57:31 +0100 Message-ID: To: =?UTF-8?Q?Tim_D=C3=BCsterhus?= Cc: PHP internals Content-Type: multipart/alternative; boundary="000000000000b03cb305f7f5677b" Subject: Re: [PHP-DEV] [RFC] Define proper semantics for range() function From: george.banyard@gmail.com ("G. P. B.") --000000000000b03cb305f7f5677b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, 28 Mar 2023 at 08:29, Tim D=C3=BCsterhus wrote: > Hi > > On 3/28/23 00:36, G. P. B. wrote: > > I therefore propose the "Define proper semantics for range() function" > RFC > > to address the unintuitive behaviour that sees no usage and/or hide bug= s: > > https://wiki.php.net/rfc/proper-range-semantics > > The "ASCII code point range" example is confusing, because it is a > decreasing range. However decreasing ranges are only introduced in the > next example. > > Best regards > Tim D=C3=BCsterhus > I've reordered the example and added a more descriptive ASCII code point range example first! I've also added an example which highlights the behaviour with null and how it would emits deprecation notices. Best regards, George P. Banyard --000000000000b03cb305f7f5677b--