A peppered AES-encrypted Argon2 encoder for Crypt::Passphrase
Changes for 0.008 - 2024-04-07T13:41:40Z
- Add support for aes-cbc-pad and aes-ecb-pad
A peppered AES-encrypted Bcrypt encoder for Crypt::Passphrase
Changes for 0.002 - 2024-04-07T13:38:27Z
- Add support for aes-cbc-pad and aes-ecb-pad
test for trailing whitespace in files.
Changes for v0.4.0 - 2024-04-07
- Add the abs_path_prune_re parameter.
- Cleanups and updates ( dist.ini / etc. )
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; }
I have a book on cleaning up old perl code but it is now a very old book LOL, will moving the subroutines to new files break old code that depends on Cat.pm? TIA
submitted by /u/bug_splat
[link] [comments]