An OpenDocument management interface

Changes for 1.200 - 2024-04-06

• Remove given/when constructs (thanks Jim Avera)
• Silence "Unknown method DESTROY" warnings

Implementation of various techniques used in data compression.

Changes for 0.04 - 2024-04-06

• ADDITIONS
• CHANGES

A module that performs semantic similarity in PXF/BFF data structures and beyond (JSON|YAML)

Changes for 0.06

• Renamed --primary-key to --primary-key-name and --set-primary-key to --generate-primary-key in csv2pheno_ranker for clarity
• Updated docs
• Changed from perl:5.36-bullseye to perl:stable-bullseye in Dockerfile
• Excluded `NA`, `NaN`, `undef`, `{}`, and `[]` from coverage_stats counts
• Freezed a few modules in requirements.txt

Find a Date in Text

Changes for 0.08 - 2024-04-06T10:32:47Z

• Use Test::Needs parse(): fix support of being given an object Fix parsing a ref to a scalar

mysqld runner for tests

Changes for 1.0030 - 2024-04-06T14:22:15Z

• Support DBD::MariaDB

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]