install.pl: Installs artifacts where they need to go in the system.
build.pl was the most complicated, but that's not saying much, it was incredibly easy to make and it's small. It even supports parallel jobs and not rebuilding an object if the source file is older than the object.
@Serpent7776 I’m sorry to hear about the warnings lost in the output.
Since you’ve got #Perl v5.38.2, write use v5.38; and in addition to strict and warnings you enable the following niceties from https://perldoc.perl.org/feature :
bitwise
current_sub
evalbytes
fc
isa
module_true
postderef_qq
say
signatures
state
unicode_eval
unicode_strings
Anyone here have experience updating a Dockerized Perl application? Specifically I am looking for help upgrading the app from 5.26 to 5.30 and how to rectify errors where some libraries (I think?) were built for Perl 5.26 and won't work under 5.30?
@philsplace @perl “[#Template languages have] two problems: First, their little language is crippled. If you need to do something the author hasn't thought of, you lose. Second: Who wants to learn another language? You already know #Perl, so why not use it?“
Started reading ‘Modern Perl’ on the train to work the other day. #Perl was the first programming language I learned, 20 years ago now, but I’ve hardly used it in probably 15 years now.
Not yet sure what I’d use it for, though. Better shell scripts? I’d normally choose Python/Ruby for that.
I work Cybersecurity, I mostly use #Perl for quick one-off scans when someone asks me, "are we vulnerable to XYZ?" when XYZ has a (mis)configuration element to it.
A lot of my hobby code is using #Rakulang these days as I really enjoy the language's mutability.
You might even consider making a reasonable case to move the project’s remaining assets off #SourceForge. Impotently whinging about it here doesn’t change anything.