Hey, #perl devs. Do you use DBIx::Class::Schema::Loader? Do you also use Perl::Tidy? You can get disappointed if Perl::Tidy reformats the dbic files, so drop this in your .perltidyrc to stop that:
Ignore DBIC-generated content
--format-skipping-begin='#(<<<| DO NOT MODIFY THE FIRST PART OF THIS FILE)'
--format-skipping-end='#(>>>| DO NOT MODIFY THIS OR ANYTHING ABOVE!)'
@tripleo If you want decent integration with 3rd party stuff (google APIs, amazon, etc...) you may need to write your own client stuff as most big service providers seem to have forgotten that #Perl exists
@tripleo#Perl’s “sharp edges” are mainly early syntax and features that later experience with large and networked #programming found dangerous, but are preserved for backward (and we do mean “backward”) compatibility.
See the details of the strict and warnings pragmas, and successively missing items in feature bundles:
I'm handling sponsorships for this year's Perl and Raku Conference. Please share this far and wide so that we can get as many new sponsors as possible. ❤️
Everyone! If your #business depends on #Perl or #RakuLang please consider supporting the communities you rely on!
One good way to ensure a sustainable future for #OpenSource ecosystems like these, is to support active and fertile venues for learning and teaching these technologies.
Right now, you can help by supporting the Perl and Raku Conference, and later this year, the London Perl Workshop.
Is this relevant for you? Forward it to your manager! 💯
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.
Now, would I use this in a big project? No way lol.
I can imagine things like subprojects would be a nightmare, and i'm a big fan of Meson/Muon. But it was a fun experiment to see what it's like. (Also, easier to make than a makefile, fuck makefiles.)
@mjgardner Thanks, I have both use strict and use warnings, but the script produced quite some lines of output and I guess the warnings got lost it the output. I guess I should've redirected the output to a file to have stderr more visible.
I'm on perl v5.38.2 and I didn't know about use v5.36, but I'm not sure it changes anything.
@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?
@dave I usually solve that by installing the system package for the troublesome module. If available of course. Otherwise installing the dev libraries can help as well (with apt).
With MySQL I couldn’t install the new v5 version on the latest Perl 5.38 version so stuck with v4. For me that requires changing the version in my cpanfile.
If I’m not mistaken the official Perl Docker images come with most stuff installed.