Automate the Firefox browser with the Marionette protocol

Changes for 1.55 - 2024-04-06T12:22Z

• Fixing 32 bit architecture test regex for x86

Number of occurrences of string/regexp pattern as sort key

Changes for 0.001 - 2024-01-23

• First release.

Perl Data Language

Changes for 2.087 - 2024-04-05

• Slatec PCHIP routines now have idiomatic [io] `skip` Pars, with doc fixed to match SLATEC code (#468)
• Slatec ezfft* routines take IFAC to avoid treating part of float array as integer (#468)
• add has_badvalue method for whether ndarray has per-pdl badvalue (#469)
• fix Slatec breaking PDL::Stats (github.com/PDLPorters/PDL-Stat…) - thanks @sebastic for report
• fix long-standing mistyping of large negative IVs on 32-bit (#469) - thanks @sebastic for report
• can now set badvalues that are Math::Complex objects (#469)

Any new developments in webperl ?

webperl.zero-g.net/

submitted by /u/ReplacementSlight413
[link] [comments]

Greetings monks, question about reorganizing a Perl module, and if the following is a good approach:

The module is 7300 lines in one file and has 106 subs. I'll call it Cat.pm, its mostly called as an object like Cat->new(); but could be called like Cat->black() or Cat::Black::meow

To simplify maintaining this file I am thinking I can make a new sub directory in the same folder as the file call it Cat/ and move the 105 of the 106 subs to about 12 or 15 new .pm's in the new folder.

I plan later to rewrite one or more of those as XS modules. Cat/Tabby_XS.pm etc.

Then in Cat.pm I would just have use Cat::Black; use Cat::White; use Cat:;tabby; ...etc in Cat.pm

The only sub I'd keep in Cat.pm is sub new which looks like this:

sub new { #Object Interface #http://www.perl.com/pub/1999/09/refererents.html my $type = shift; my $self = {}; $self->{dbh} = shift; bless $self, $type; $self; } 

submitted by /u/bug_splat
[link] [comments]