Groups | Search | Server Info | Login | Register


Groups > perl.perl5.porters > #99869

Assistance requested to complete "Modernize the PRNG" PR

Newsgroups perl.perl5.porters
Message-ID <feae9b8e-9956-42cd-87da-9ff88df47fc3@perturb.org> (permalink)
Date 2026-03-04 15:51 -0800
Subject Assistance requested to complete "Modernize the PRNG" PR
References <20260126171328.25b0b4ab@vel.leo> <fd343cc3-ee4e-4759-9a24-df32ba0b29f7@perturb.org>
From scott@perturb.org (Scott Baker)

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

I'm still looking for a knowledgeable Perl internals person to get the 
*Modernize the PRNG *PR across the finish line. 90% of what we need is 
already in the PR <https://github.com/Perl/perl5/pull/24105>. Per the 
comments on the PR we just need to make it threadsafe.

That is beyond my skillset, and something I'm not super comfortable 
poking around with/at. Is anyone interested in getting the *Modernize 
the PRNG *PR the last three yards across the goal line. That's an 
American football reference, I'm not sure what the equivalent would be 
in soccer.

-- Scottchiefbaker

On 1/26/2026 3:16 PM, Scott Baker wrote:
>
> 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
>>

Back to perl.perl5.porters | Previous | NextPrevious in thread | Find similar


Thread

PSC #213 2026-01-26 leonerd@leonerd.org.uk ("Paul \"LeoNerd\" Evans") - 2026-01-26 17:13 +0000
  Re: PSC #213 2026-01-26 - PRNG pull-request update scott@perturb.org (Scott Baker) - 2026-01-26 15:16 -0800
    Assistance requested to complete "Modernize the PRNG" PR scott@perturb.org (Scott Baker) - 2026-03-04 15:51 -0800

csiph-web