Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:118914 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 27296 invoked from network); 30 Oct 2022 01:02:54 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 30 Oct 2022 01:02:54 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id DABF81804BA for ; Sat, 29 Oct 2022 18:02:52 -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-vs1-f48.google.com (mail-vs1-f48.google.com [209.85.217.48]) (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 18:02:52 -0700 (PDT) Received: by mail-vs1-f48.google.com with SMTP id k1so8300606vsc.13 for ; Sat, 29 Oct 2022 18:02:52 -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=8jJ00FVC01eBJ0yLgfNLarb1Lb6I/DsJm/ihIV90MTE=; b=jJW9x/RzE5+kpet3AHLEdWO8wkwC7zUXRO4dxzKpnEYC5jcRq9443hIFCWaVIcjn6M Q2fIXzYKCs8DZrJPUZYqd2dzzALg6FY2TuxwIzS0a2iaD5dJ2JIYPUxlsffh5M5p5dz5 XQ/ohNHSjjDfAghFYkOJBmEBQokFbA6cOBnAmbS82m3qn6yMo/ojFw64i99lZXQckIWT IMgUe8tlX2d1GfYF7PxkkeBgbcyvPMfnnhZ298KjhmRXI0OCFMFxLh/fgKGU/S+fyHvq 906o7r35Foq8pgfp/jthyQwdSmzvqdKn7NfC2u/lYZ5EB29Mctg0CwjO+hmhAng17Fo5 BPwQ== 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=8jJ00FVC01eBJ0yLgfNLarb1Lb6I/DsJm/ihIV90MTE=; b=L7hEE3CpD8OKfJrAByfmxqNbGQLc3Ni+h6C+0CghwaLhO/n7AKxn4WGMTR18EVESyn HbcplLCEeeh1bcaGiU+9gPOcYpbfHZQODaq7siWgmYc0XRa4Qwv9tZcvczXk/Bo78sQy dOPpOpPCDqGqDEme64PrEz3g+mIlERZ0jMc5/lY7U/8YvNRKn72u/wIYyVAe3Lz2ABQz 0PaD9quRWkXxVEYRf3ZrjXTqYCPsZbeKi2IilNCLyt+twNVBwxhtIzPcDmJsIzqcb0zA RA9aux9BdWEV/5rnCwBS10JcNg/YpCMu6vbLv8+5Y64pZPAG7qIaef4fWVW/Y7AgqiJZ 5iTg== X-Gm-Message-State: ACrzQf2HfcONSMlolRHnvFtgP1YsbdyLjd1QyL95zfoHV4L9Y9RT3cAI hE6lfYqfhPnIF7swmKuMsc41gWRRoIjvhAQLK2Nh8eQR X-Google-Smtp-Source: AMsMyM4Zcc06UIjbd00QMISTNJlJLBmyL5iw++y1T9LkJ5nx3CQ9Q2HdoPhVWVg/8MJOgqEKOFa9vKYWJx8zDitCVUQ= X-Received: by 2002:a05:6102:365a:b0:3ab:e987:e4b3 with SMTP id s26-20020a056102365a00b003abe987e4b3mr2082296vsu.84.1667091771499; Sat, 29 Oct 2022 18:02:51 -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 18:02:39 -0700 Message-ID: To: Claude Pache Cc: =?UTF-8?Q?Joshua_R=C3=BCsweg?= , PHP internals , Larry Garfield Content-Type: multipart/alternative; boundary="000000000000d92b2905ec360c64" Subject: Re: [PHP-DEV] RFC [Discussion]: Randomizer Additions From: jordan.ledoux@gmail.com (Jordan LeDoux) --000000000000d92b2905ec360c64 Content-Type: text/plain; charset="UTF-8" On Sat, Oct 29, 2022 at 12:21 PM Jordan LeDoux wrote: > > > > 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 > On second thought, isn't it possible to simply choose a random integer to correspond with the char list position instead, sidestepping the UTF-8 issue entirely? In which case, it might be more accurate to name it just `getRandomCharFromList` Jordan --000000000000d92b2905ec360c64--