Re: PSC #213 2026-01-26 - PRNG pull-request update

I was able to get my PRNG pull-request passing *all *unit tests on *all 
*platforms today. I think the PR is "close" to being complete.

Both of the comments on the PR are related to the current implementation 
not being thread-safe. I spent 45 minutes trying to untangle the defines 
and macros that wrapper the PRNG functions and my brain just gave up. I 
understand enough C to implement a PRNG, but I don't know enough of the 
Perl system to handle the 14x layers of wrappers and variable mapping.

In it's current state, the PR is merge-able and passes all unit tests. 
If it needs to be made thread-safe, someone else will have to get it 
across the finish line.

-- Scottchiefbaker

On 1/26/2026 9:13 AM, Paul "LeoNerd" Evans wrote:
> All three of us discussed:
>
> * We agree with the general idea of an improved PRNG, so we encourage
>    Scott to continue working on [PR #24105][1] to get it into a polished
>    state ready for merge
>
> * Haarg's ["missing import" PR][2] now looks good; Paul has LGTM'ed it
>
> * TLS in core still remains a goal for the next release cycle.
>    [`Crypt::OpenSSL3`][3] might now be in a complete enough state to
>    support a minimal viable product "https" client to be built on top of
>    it, that could be used by an in-core CPAN client
>
> [1]:https://github.com/Perl/perl5/pull/24105
> [2]:https://github.com/Perl/perl5/pull/24059
> [3]:https://metacpan.org/pod/Crypt::OpenSSL3
>
> https://blogs.perl.org/users/psc/2026/01/this-week-in-psc-213-2026-01-26.html
>