Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:118233 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 50654 invoked from network); 9 Jul 2022 07:28:49 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 9 Jul 2022 07:28:49 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 080F8180211 for ; Sat, 9 Jul 2022 02:22:32 -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=0.6 required=5.0 tests=BAYES_50,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM, 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-wm1-f44.google.com (mail-wm1-f44.google.com [209.85.128.44]) (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 ; Sat, 9 Jul 2022 02:22:31 -0700 (PDT) Received: by mail-wm1-f44.google.com with SMTP id v67-20020a1cac46000000b003a1888b9d36so2411506wme.0 for ; Sat, 09 Jul 2022 02:22:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=date:from:to:subject:user-agent:in-reply-to:references:message-id :mime-version:content-transfer-encoding; bh=HwRs+wPJ7GjSCU3r+gGuhR3P58hwEc7qBFkZcWZJ+8M=; b=EMjlHZUIttvS+qvW/ukjW0kQaJuKP6Sgc2gfPyCofgw7k0DWxROc9WgmpjIp0TI8nU Ii4pw9zL/FSY6DRceMQHTCL8zhSvH6Ymmkdn2fDzgSbHKxlfCh1e+8GfY0e26m/v7KTL zuZrhoJiRLCF1R6siVE1d30BEhnfBnqZ1s3tDojFB7cVpec8ookawJi/5/hJzMhXqcLa o9L944cQ+1CyVDdOOFAMMUXq4uxksioHfrIPySfybWjuMf1SVL/JrA1af3l94p8PtjFT fSoS7tIJJ9LsSREans1kO5hk5HAw2JawmO+DMweEsWQMxu+7LSE51YsaEYVT38SWJmvb 8yeA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:subject:user-agent:in-reply-to :references:message-id:mime-version:content-transfer-encoding; bh=HwRs+wPJ7GjSCU3r+gGuhR3P58hwEc7qBFkZcWZJ+8M=; b=7b4BVzKNc/otUDEmMiWBxbGcB3vZEo8oRngi8JcBbP/Gedo+P4pKFaPcpZnaCDQ4lx ztWj7B3DPWC30oPPToC9EUY5ckK+WtroS9epjfGvQE1E8UpP0UU8dspS8Ah+/7eFZPcL oX3V+XZX0/lthqTvdk8WbcPQ6PcnQlSG+x21AmP4fJAjmU3gTBjjS9+qmYC+qIyTCYlQ yzmssJXLbgzGzLCQwpLwqoHXEoJ64zQZkdwT+9vkFLsYFBxspcfl2+b5S3vr4GnV3k5D lo1u3o9NCQ5rl672GlanMyEvEV+CoKzMq0JrqOWyMAcnMKik5ITAtIo1COKA/sRNEE+M Vbsw== X-Gm-Message-State: AJIora9IxVh5HlwwnztDegiSiWzTgaG09AGzlOKMClVQaUxZVsnofr/e kcriLRE7Mm+pL96DozwoQh0G1ASNC7M= X-Google-Smtp-Source: AGRyM1uRmDZLxFFo9hprPeOCiXTplg1yk5LcpzHB5VlmgOycVpEybnt+aLHSRw6/8/rMEWExT72AEg== X-Received: by 2002:a05:600c:35ca:b0:3a2:aee3:a8ff with SMTP id r10-20020a05600c35ca00b003a2aee3a8ffmr4418550wmq.206.1657358550572; Sat, 09 Jul 2022 02:22:30 -0700 (PDT) Received: from [127.0.0.1] (cpc104104-brig22-2-0-cust548.3-3.cable.virginm.net. [82.10.58.37]) by smtp.gmail.com with ESMTPSA id q5-20020adf9dc5000000b0021d928d2388sm951939wre.85.2022.07.09.02.22.29 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 09 Jul 2022 02:22:29 -0700 (PDT) Date: Sat, 09 Jul 2022 10:22:22 +0100 To: internals@lists.php.net User-Agent: K-9 Mail for Android In-Reply-To: References: <1657331615.886786918@f311.i.mail.ru> Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] Re: Character range syntax ".." for character masks From: rowan.collins@gmail.com (Rowan Tommins) On 9 July 2022 05:02:21 BST, mickmackusa wrote: >Thanks for your reply, Kirill, but I am no way trying to introduce a new, >general use operator for all encountered strings=2E > >I am purely focused on having the operator consistently implemented for a= ll >character masks=2E I think the confusion here comes from your use of the word "operator" - in= a technical sense, this is not an operator in the language, which takes tw= o values or expressions and produces a new value=2E Rather, it's a conventi= on used inside certain functions, to interpret a string argument in a speci= al way=2E I suppose you could argue that the result is a very simple embedd= ed language, like regular expressions, and then '=2E=2E' would be an operat= or in that embedded language; but it's probably not how most people would d= escribe it=2E As for proposing to add it in more places, it would be good to have a clea= r expression of why having this facility in those functions would be useful= =2E Every extra feature adds complexity, and is a potential source of bugs = both in its implementation and in code that users write which touches it=2E= A proposal needs to make a clear case of the gains that outweigh those cos= ts=2E Regards, --=20 Rowan Tommins [IMSoP]