Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:118913 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 11261 invoked from network); 29 Oct 2022 19:21:34 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 29 Oct 2022 19:21:34 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id D2EE81804F7 for ; Sat, 29 Oct 2022 12:21:33 -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-ua1-f42.google.com (mail-ua1-f42.google.com [209.85.222.42]) (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, 29 Oct 2022 12:21:33 -0700 (PDT) Received: by mail-ua1-f42.google.com with SMTP id c31so3339769uae.10 for ; Sat, 29 Oct 2022 12:21:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=ZH7ng0LWCtVLZpwBnkYVuLa8AafhO5Zz+yuE6QurkQY=; b=qPf057u2qVJOmDEJapAqKofwAxbWcfw5kodofpUTWXNeBRSoV53H3kxNqtsP0luRVu UTP6oDWTEP35i4Gsa6SndaUP8W3c8m2LRUWchQhetRFfn+5sEZcwUifjzqEbkraA/ejV FsnKCOuvwuiizFHYohQ/XqzbtV4gqBuIpvA7ONExnvOUIndlYI9bq30oKhhy08sNByei Tp1pTUwb0OdCWzncFzAFkMeKauf6LUjLs5VedA0DKnvxSbbnrUVfgu3p6iJ+NAE2pgn/ N5hca/493ogKsNwjZEZ5KVzPfvTegeb8UvLb2HRgvpiAPpebV3i8oNCF9c/fX6OdkdGE 3NDQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; 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=ZH7ng0LWCtVLZpwBnkYVuLa8AafhO5Zz+yuE6QurkQY=; b=7oSD0Z2QCB1n2eyLd6C2v7INF9L4Yw15cZV/lgtMFQ7V9jvqyr0VFRq8YfX/IjQG4y q9p3OZg60+T5SUvrRgfZzOuxbYIB3BmeKSIcJYYeArMbE+VF/pkjcTdkBrot7O8GfP6N rvrbH1aGhNSceOHRLP2kd4laG1NS4iga/TiWAYKB+4wfHo1iwZs7XgF5DkyKhVTS26yD LyJmDALNUHPKDCnzqW971LBjEg/hZK8l1ZnRD7UKcREHjDf0fJRZYygqhSiRVCEMN179 KUWtIXzy9N4tOI6VoEDvSRb9bWleUXNCH4NI0oE0zF/J3v6M7iw3NJeDxHTiCLgSVj8g 9lZQ== X-Gm-Message-State: ACrzQf0LDIJVx101MSrbX/Q1Uhxq4raCgLnIIYvM50Eq0QmCKCSLa3gh QTxrTPlblFE+vYTauB51yrD17QuRb1QGxNGw6YA= X-Google-Smtp-Source: AMsMyM5FxIgx0uVlpeM/mQ++HphD+eEBmtadxamg6S+aYRZj8YU1lbd/jbmZlk6r0ORXZGMlX1Eho51u+cjblCqnFVA= X-Received: by 2002:ab0:70c6:0:b0:39e:ed14:806b with SMTP id r6-20020ab070c6000000b0039eed14806bmr2131466ual.82.1667071292687; Sat, 29 Oct 2022 12:21:32 -0700 (PDT) MIME-Version: 1.0 References: <5ceebae4-a3fb-5d29-cdb7-dceed7b07c78@wcflabs.de> <71552420-ae73-4404-b149-49e73ec29d20@app.fastmail.com> In-Reply-To: Date: Sat, 29 Oct 2022 12:21:21 -0700 Message-ID: To: Claude Pache Cc: =?UTF-8?Q?Joshua_R=C3=BCsweg?= , PHP internals , Larry Garfield Content-Type: multipart/alternative; boundary="000000000000374ab105ec3148a5" Subject: Re: [PHP-DEV] RFC [Discussion]: Randomizer Additions From: jordan.ledoux@gmail.com (Jordan LeDoux) --000000000000374ab105ec3148a5 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sat, Oct 29, 2022 at 6:10 AM Claude Pache wrote= : > > > > Le 28 oct. 2022 =C3=A0 23:43, Jordan LeDoux a > =C3=A9crit : > > > > On Fri, Oct 28, 2022 at 12:30 PM Joshua R=C3=BCsweg via internals < > > internals@lists.php.net> wrote: > > > > Not to try and bikeshed further, but wouldn't `getBytesFromChars` or > > `getBytesFromCharList` be more clear while being nearly as accurate? > > > > Jordan > > > In the face of multibyte character sets such as UTF-8, I wouldn=E2=80=99t= use > =E2=80=9Cchar=E2=80=9D to mean =E2=80=9Cbyte=E2=80=9D (even if, in practi= ce, the most common use will be > strings of 1-byte chars). =E2=80=9CAlphabet=E2=80=9D or =E2=80=9Cstring= =E2=80=9D might be ambiguous (is it > an alphabet of bytes or an alphabet of characters?), but at least they ar= e > not contradictory. > > =E2=80=94Claude Well... perhaps. But "get bytes from character list" would do exactly what it says it will do, even from UTF-8 strings. It will use any of the bytes from the character list, even if one character in the list may contribute multiple bytes to choose from. It is *not* contradictory, just potentially confusing about the result Jordan --000000000000374ab105ec3148a5--