Very configurable Markdown processor written in pure Perl, supporting the CommonMark spec and many extensions

Changes for 1.01 - 2024-04-05

• Deactivate the support for setext headings in pmarkdown default syntax.
• Remove a copy of the input Markdown when using the functional interface.
• Bugfixes:

Provides generalized and structured configuration value access

Changes for 3.01 - 2024-04-05T12:32:18-05:00

• declare correct min perl version
• provide more/better exaples in SYNOPSIS docs

mysqld runner for tests

Changes for 1.0020 - 2024-04-05T16:35:54Z

• introduce GitHub Actions for CI
• Use UNIX socket authentication with MariaDB 10.4.3
• ignore-db-dir on MySQL 5.7 only
• Don't loop endlessly if mysqld fails to start
• Replace which with command -v for POSIX-compliant
• fix Test 05-copy-data-from.t Fails

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]