A SQL Database object abstraction class

Changes for v1.2.2 - 2024-04-05T15:33:06Z

• Corrected a bug when version of DBD::SQLite < 1.71 is used and thus doe snot have the constant DBD::SQLite::Constants::SQLITE_TEXT

Interface to TinySoundFont, a "SoundFont2 synthesizer library in a single C/C++ file"

Changes for 0.12 - 2024-04-05T00:25:30Z

• Update TinySoundFont to newest commit

find perl root and push lib modules path to @INC

Changes for 0.06 - 2024-04-05T02:25:56Z

• update tests. smoke test reports failing for darwin
• update docs for sub root feature that returns root dir

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]