Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:120305 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 30565 invoked from network); 15 May 2023 22:53:28 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 15 May 2023 22:53:28 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 10F361804AA for ; Mon, 15 May 2023 15:53:27 -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_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-lj1-f176.google.com (mail-lj1-f176.google.com [209.85.208.176]) (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 ; Mon, 15 May 2023 15:53:23 -0700 (PDT) Received: by mail-lj1-f176.google.com with SMTP id 38308e7fff4ca-2ac7c59665bso145692331fa.3 for ; Mon, 15 May 2023 15:53:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1684191202; x=1686783202; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=NnzuXSoCf9nSsetLQ2vsxmeDLRnROfq/55/LeBa4VfE=; b=FO1ZnStqDD8fuv1TPPObCFHSDaQW53QYZAyZGrQoNPwxlzAWdZ6mxEbqbk3t+MAE90 l9XM1sO17GRtJkOsP8eBKhmHtLo2n8cb2QZtmD5fiTfmR2LEH6Uty4Gd98Vz9lhisqaI xLTZeTXMCkMRlJXX23ulaykCeBlp9OlIbrCN4uU9Y2Op0uv8koUDophadY1uXUEpXEe7 sC+/+HkfN6WzkoE6MXFKfNr0T2+9dvonb+hSAAfltwlYxua0gMKed7xPS4UjUxMXDS4l IotH7Mxfeq+cm4A++mw74sugQChHVT/XY0ZLF0XQDiudH36Cf5+lOLQb71fZn/DuckfY fwbg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684191202; x=1686783202; 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=NnzuXSoCf9nSsetLQ2vsxmeDLRnROfq/55/LeBa4VfE=; b=hdEKcKsoXreNq38zsnNxhnJECo2ApLeS0XE2bL8doeTc68xvFY+0y+2H9vXXjptdsS dibYebsk3ulqu1P4Hp1eKYnYDca1+YFNKj8wdZoVjedaG/Wf3a6bAd9p4v85iF81i5IC too0D7+oRNmEbMS1q9fNfFi8EI4w2HdLijWr8vmZhgBzlYMBGM+Aze8b08V18rO0BLEg Cso4PEKQBZMzBlxmNOucuO4RJIjn4QtLtgasn+qacUMDwjfr9fix+F/ABD/VfF9l82T7 b1e1JZjGCBuyOcGK9/c3cW1mkx2IgB9wWn474f6Wv2cgLcX7lks3MrKviEl/427jKWAd jGHw== X-Gm-Message-State: AC+VfDzcmNvnwYE7sOtcV0maKT3Tj+VMK9q8OoK+64qdks7vcDyy2Eio 8xPG8YDJ4f8gRTZVGuUrLbtB3Tpz20IlUtkFmkQ= X-Google-Smtp-Source: ACHHUZ57trs1nyv2mvX3O4x8i9FNk1NS+u6IErqZmjeZf03GN9yAAVV8z+TPjDrGPAiysROnZOuUFiCrTZy4v1Zl87o= X-Received: by 2002:a2e:9c54:0:b0:2ad:a955:dfa3 with SMTP id t20-20020a2e9c54000000b002ada955dfa3mr6330289ljj.9.1684191201512; Mon, 15 May 2023 15:53:21 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Tue, 16 May 2023 00:53:10 +0200 Message-ID: To: "G. P. B." Cc: PHP internals Content-Type: multipart/alternative; boundary="0000000000004cd26105fbc35288" Subject: Re: [PHP-DEV] [RFC] Define proper semantics for range() function From: jorg.sowa@gmail.com (Jorg Sowa) --0000000000004cd26105fbc35288 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello! I have one concern about the part: > Emit an E_WARNING when $start or $end is cast to an integer because the other boundary input is a number or numeric string. (e.g. range ('5', 'z'); or range (5= , 'z');) Doesn't it limit the functionality of the function for the numbers as characters? Currently when we call range('/','z') we get full range of characters. https://onlinephp.io/c/9cb12 But when we change argument $start to next character which is zero ('0') then we get array with only one element. https://onlinephp.io/c/a0cda Casting numerical string in this function may be confusing. Sorry for making fuss just before voting, but didn't see this topic before and wanted to share my insights with you thinking it may be relevant. Kind regards, Jorg On Mon, May 15, 2023 at 4:42=E2=80=AFPM G. P. B. = wrote: > Hello Internals, > > I plan to put the RFC to a vote tomorrow in its current state, which has > not been changed since the 30th of March: > https://wiki.php.net/rfc/proper-range-semantics > > Any final comments or complaints should be raised now. > > Best regards, > > George P. Banyard > --0000000000004cd26105fbc35288--