Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:118915 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 28777 invoked from network); 30 Oct 2022 01:08:09 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 30 Oct 2022 01:08:09 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 6210D1804F7 for ; Sat, 29 Oct 2022 18:08:09 -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-f54.google.com (mail-vs1-f54.google.com [209.85.217.54]) (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:08:09 -0700 (PDT) Received: by mail-vs1-f54.google.com with SMTP id t14so1132352vsr.9 for ; Sat, 29 Oct 2022 18:08:08 -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=hw4FOoSwWUWz53NOy+hPUZUCGevVQ59/6KZ0tHqkkXM=; b=JCCi5U0blCj/RKEAaCUqjqH/cTjGOTisCrAS/7Hn14h/4c45NJTh/oq6L75ik4/DcW 9wdtjC4CSOym6RPCfayddSJ7MZoJ+M3I8n1bsbdNWHDBr+czCc+CSH4CXtwjvRobF2EH QT8HaKkCTSYA2mIn3RPd65n9UoOLc2RvdLa2o2gznq+UQTnTq7UGfDdTRSUdXVFjTYWB Xu1TE1okrTS1BHql6/gkmhh77XPniW4HgbfEJakvjZb4PIHSuD2VUC9JMs5pQKCNVB01 XVDxkWNP+JFWnj4CKv4KcBxsyjKtaVNW6lsMSQ4fquUwoJyK1sCdJ8KejalL4TPph90s 5DUw== 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=hw4FOoSwWUWz53NOy+hPUZUCGevVQ59/6KZ0tHqkkXM=; b=Z2IUoQpOQSLEh+IGn9EFu+XX3UePwJb9tRN4YNa2Mkarzimedc6aSSU4gNZfDOLpXo gkKgxdstxEX7gGJb4grOvZMtSz3aDwVPLz6rQzEI9nZ6Lw5+2vkgogwp83iEzCppn/OV Rlxnl4PudYRg+PSEHiOZPGvoJBqKlJ+nRai86M1Ng92gIcjlfAmoU9TzCun6KFtf/O9H jS1x+QyHp7xqfZvuq65aco/0vBrfOsuSf7xqldBxYvw00eNX3n3LZRwmA2ATjJ5xEAcq klwXzvb+XWORy9Vu8dqcsc1a2xmz0pFHyKkGyzsZ04NIwVuDfh1UNb8NNStp/2iqnNuF rtCA== X-Gm-Message-State: ACrzQf2adDX6hkRT9oO1+HgRv66jcoQto17upGoWgwY8Jth81aIN/5gQ l8o2cVyoSK5ctgAOe3MylRjwQA4XGg0N8sLvDiM= X-Google-Smtp-Source: AMsMyM70VdMy42Zm1L3oVATubACpGh88UGgg8fEM4aKVeo2hiWI82UiKcPio7KFx1XkQ72j5seSqDTnk0eKxDLoNzzU= X-Received: by 2002:a05:6102:365a:b0:3ab:e987:e4b3 with SMTP id s26-20020a056102365a00b003abe987e4b3mr2086223vsu.84.1667092088329; Sat, 29 Oct 2022 18:08:08 -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:07:56 -0700 Message-ID: To: Claude Pache Cc: =?UTF-8?Q?Joshua_R=C3=BCsweg?= , PHP internals , Larry Garfield Content-Type: multipart/alternative; boundary="000000000000bb9c8105ec361f3e" Subject: Re: [PHP-DEV] RFC [Discussion]: Randomizer Additions From: jordan.ledoux@gmail.com (Jordan LeDoux) --000000000000bb9c8105ec361f3e Content-Type: text/plain; charset="UTF-8" On Sat, Oct 29, 2022 at 6:02 PM Jordan LeDoux wrote: > > > 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 > Nevermind, disregard. I just remembered (again) how strings are handled in PHP and why this wouldn't work. Jordan --000000000000bb9c8105ec361f3e--