Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:120319 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 26093 invoked from network); 16 May 2023 19:37:41 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 16 May 2023 19:37:41 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 3A63A1804D0 for ; Tue, 16 May 2023 12:37:41 -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-pf1-f174.google.com (mail-pf1-f174.google.com [209.85.210.174]) (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, 16 May 2023 12:37:40 -0700 (PDT) Received: by mail-pf1-f174.google.com with SMTP id d2e1a72fcca58-643a1fed360so9085067b3a.3 for ; Tue, 16 May 2023 12:37:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1684265860; x=1686857860; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=6ABEPQSJxqZwYWI2ylV5XixlS3QLZC39b7FagDSs5IE=; b=pXYBs5/yvb7LTGSb8vmND7HpMzDSzsbCgRm5VHhjr4pS8GP42wTQzZEyPyKKk4BciS KQ9Nf/RtMtRxt2nyr4dYkq7hoE/OcJYAtvl48cbr89tQg6ghLJJtYI7Vh1LqFBDOD0tq jf+7QssWBMJ1IMLnHfXmBCVgBIzxQL/8qrLwB5d3tClvTFCcJ/l1s6JYHSVmLX5A0nyV PkoM4fCVR+wg2UpLCaxAkL4xoA4dy6dNPVfb1MJQEdEOXQCKMxqoNz7vUzdaR2YiBhGf C/Ro6XyTsWdJayyMIZXUj7vAQCPN9qvGPWTa0mytlW/wiKTe6SQEaC2aB04zjYc5/Rhs AfVA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684265860; x=1686857860; 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=6ABEPQSJxqZwYWI2ylV5XixlS3QLZC39b7FagDSs5IE=; b=dZLXxEvabLqNybvkQ9MqKE2B+PS/loSW+VVRH98Qom7WE0IF+vfEIZdNxSAFExsuFN y6OoQIKzQCjhGTCyE2c3fvmmlzC9vWobhGAz6M8QDiauiWxCo8DA7jbjir0cvHSYtsu4 qmHKoi/tIkNb5PlQ2h72y+/P+72UpGctMDqESiVHzjI+NiVnOy0I8WRzCweatVjyAS53 00p5E5pPUwl5fqvHV3depbVRAzd7TlvViK25Rse1idW5l6wNbdhWIdjAjiSIjeJ2T6Cv cXjQQD8gxH6lXE3ddyeBdfsZBnygP4NhORlKVnvZIpbzN33+RKxTgHiQ8prlVmLRJSOr aEXQ== X-Gm-Message-State: AC+VfDz8g9YGdmbNiHWY4FtkQNGY7t+j8yUCohus2xwYSatCzqrjzWRz Gxjl6NWxGHhmkewbhUoSEqVuaBXRs/AcGemUtOQ= X-Google-Smtp-Source: ACHHUZ43lNCJrd7wLCTXxGKR5JWCEtytuXGLdt1XJglFy1m4U8NHJVfDw+QKxXSKbO3zqab9JoP2HhJLD3LdYCModxQ= X-Received: by 2002:a05:6a00:814:b0:64c:ae1c:3385 with SMTP id m20-20020a056a00081400b0064cae1c3385mr8869465pfk.32.1684265859619; Tue, 16 May 2023 12:37:39 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Tue, 16 May 2023 20:37:28 +0100 Message-ID: To: Jorg Sowa Cc: PHP internals Content-Type: multipart/alternative; boundary="000000000000451eef05fbd4b4b1" Subject: Re: [PHP-DEV] [RFC] Define proper semantics for range() function From: george.banyard@gmail.com ("G. P. B.") --000000000000451eef05fbd4b4b1 Content-Type: text/plain; charset="UTF-8" On Tue, 16 May 2023 at 17:49, Jorg Sowa wrote: > Thank you. That makes sense. I have last question about case with integer > and string digit, i.e. range('5', 10) or range('1', 9). What would be in > this case expected output? I couldn't find any test cases covering this > example. > I've added test cases, but the RFC already mentions that those numeric strings would be interpreted as integers and thus generate a list of ints. Best regards, George P. Banyard PS: Just an etiquette reminder to bottom post instead of top posting to not carry around the previous bits of emails (see https://github.com/Danack/RfcCodex/blob/master/etiquette/mailing_list.md#why-should-i-place-my-response-below-the-quoted-text ) --000000000000451eef05fbd4b4b1--