Re^5: Should I use carp/croak or warn/die

I'm fine with Huffman* coding keywords (often used = own keyword) and naming functions is indeed difficult ...

But I'm still not happy, sorry ! :)

Cheers Rolf
_{(addicted to the Perl Programming Language :)

Wikisyntax for the Monastery}

PS: any need to explain MilliHuffman? ;-)

Comment on Re^5: Should I use carp/croak or warn/die

Replies are listed 'Best First'.
Re^6: Should I use carp/croak or warn/die by Your Mother (Archbishop) on May 30, 2018 at 17:48 UTC
I liked some of your thoughts about "nice to haves" above and I'm always open to new approaches even though I've never met Ms Huffman. I propose some replacements/aliases– carp ⇢ gripe cluck ⇢ kvetch croak ⇢ lament confess ⇢ dirge shortmess ⇢ demur longmess ⇢ expostulate Now we're getting somewhere. I am seeing an Acme:: future here; especially if it duplicates every single function in the core and in common usage from the more popular CPAN modules, with the entire thesaurus entry for each! :P ← You can't stop me!	[reply]
Re^7: Should I use carp/croak or warn/die by LanX (Saint) on May 30, 2018 at 17:59 UTC
Rather two additional generic functions which are synonymous to this range of things you like to do with Ms Milli. ;p Cheers Rolf _{(addicted to the Perl Programming Language :) Wikisyntax for the Monastery}	[reply]
Re^7: Should I use carp/croak or warn/die by karlgoethebier (Abbot) on May 31, 2018 at 20:04 UTC
"...seeing an Acme:: future here..." Great expectations. I guess putting something like `use Carp; sub lament { goto &croak }` in a role should do the job (untested). Best regards, Karl ŤThe Crux of the Biscuit is the Apostropheť `perl -MCrypt::CBC -E 'say Crypt::CBC->new(-key=>'kgb',-cipher=>"Blowfish")->decrypt_hex($ENV{KARL});'`Help	[reply] [d/l] [select]