Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:119752
Return-Path: <tim@bastelstu.be>
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 39068 invoked from network); 28 Mar 2023 07:29:54 -0000
Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5)
  by pb1.pair.com with SMTP; 28 Mar 2023 07:29:54 -0000
Received: from php-smtp4.php.net (localhost [127.0.0.1])
	by php-smtp4.php.net (Postfix) with ESMTP id 7B4CB1804F8
	for <internals@lists.php.net>; Tue, 28 Mar 2023 00:29:53 -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,SPF_HELO_NONE,SPF_PASS,
	T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.2
X-Spam-ASN: AS24940 176.9.0.0/16
X-Spam-Virus: No
X-Envelope-From: <tim@bastelstu.be>
Received: from chrono.xqk7.com (chrono.xqk7.com [176.9.45.72])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by php-smtp4.php.net (Postfix) with ESMTPS
	for <internals@lists.php.net>; Tue, 28 Mar 2023 00:29:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bastelstu.be;
	s=mail20171119; t=1679988591;
	bh=V2DQfP82OKQhEvw7u7gMcTWCvoVDvRH4oxQt4LW/f5U=;
	h=Message-ID:Date:MIME-Version:Subject:To:References:From:
	 In-Reply-To:Content-Type:from:to:cc:subject:message-id;
	b=L6jaaQFJcEjiTOETV+K34rhkVjYludpczbLVPXwcSv/mvt9m3oMuoW/H9VxFzYPO8
	 iFrGJI/HuSOmrdrddGLsM9L8zY793N3a7ISYo9hWJCwCqFQOtnegmk7mVspSD0xOWD
	 63+6b2XwB/UE5FD97Xegbp0GvNW/yd3LYh73qNA7OYt646Gxj0S679bWfGGgv36Go+
	 ZPv5ea7nuMuZ5/8dxInSYW+udO5R1ktAQc0RE4ubzZqSWa8oUq/CmPKd+NL8yTiwh+
	 LRFqHjhAYNDFzGrDpaqD0lLKTVK35pn/g9W7hdwFhecoXN8CQgArdE/7mLs4wtsldg
	 L8XlLN0vC7iXg==
Message-ID: <a409ab9c-6aa9-498f-d935-f75b80e7c6a1@bastelstu.be>
Date: Tue, 28 Mar 2023 09:29:49 +0200
MIME-Version: 1.0
To: "G. P. B." <george.banyard@gmail.com>,
 PHP internals <internals@lists.php.net>
References: <CAFPFaMJ1opg7=SZ2ovFiAqjO_z1avpcNPFWTOoOqjhptoxSvcg@mail.gmail.com>
Content-Language: en-US
In-Reply-To: <CAFPFaMJ1opg7=SZ2ovFiAqjO_z1avpcNPFWTOoOqjhptoxSvcg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] [RFC] Define proper semantics for range() function
From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=c3=bcsterhus?=)

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 bugs:
> 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üsterhus