@kittylyst @jmtd I agree that it can be readable, particularly with adequate comments which I feel are super-critical in #perl, although from experience I definitely think that perl makes it an awful lot easier to write unintelligible gibberish ;-)
Interesting that you feel that way about #python though - I typically consider that a bit better, although do you think it's because non-sw-dev types are writing python code and don't consider maintainability?
Every once in a while I'm just flabbergasted by how bad #Perl error-handling is, or at least old-style error-handling before Perl's version of exceptions started to catch on.
Like, the "messages" method of a "Mail::IMAPClient" object returns an empty list if there are no messages to fetch, but it returns undef (a scalar, not a list) if there was an error, so you can't just do "!@msgs" to check for an error, you have to do "@msgs==1&&!defined($msgs[0])". Ridiculous.
#programming
"Modern Perl" è un libro sul linguaggio perl, leggibile gratuitamente online.
Ho letto i primi capitoli e mi sembra una risorsa interessante da condividere. Ne abbiamo parlato (poco) su "Hello World", MUC amicə del GUUF.
"Perl was developed by Larry Wall in 1987 as a general-purpose Unix scripting language to make report processing easier."
#unix #unixITA #linuxITA #guufITA #guufXMPP #fedilug #perl #programming #programmingbooks #perl #helloworldxmpp
#Perl @PerlWChallenge 332 Binary Date and Odd Letters https://wlmb.github.io/2025/07/26/PWC332/
#noxp
The Weekly Challenge - 332 #Perl #RakuLang
Task 1: Binary Date
Task 2: Odd Letters
https://theweeklychallenge.org/blog/perl-weekly-challenge-332
Oh my gosh, I didn't know that Matt Trout died. He was a definite "presence" in the Perl world.
The last time I interacted with him was years ago. He was trying to convince to me to get involved in taking on XS components of some CGI-related modules. I'd have rather had needles pounded into my eyes.
I always appreciated his bluntness. And his very fast, sharp intelligence.
I didn't even know he wasn't able to work much lately. Godspeed Matt.
https://www.shadowcat.co.uk/2025/07/09/ripples-they-cause-in-the-world/
The Weekly Challenge - 331 #Perl #RakuLang
Task 1: Last Word
Task 2: Buddy Strings
https://theweeklychallenge.org/blog/perl-weekly-challenge-331
@profoundlynerdy That's a purely syntactic issue. You want (...) to be parsed as the (...)[...] list slice operator, but here say gobbles it up for the say(...) function call syntax. Two solutions:
say((split " ", "Foo Bar")[0])say +(split " ", "Foo Bar")[0](I changed split / / (which splits on single spaces) to split " " (which splits on any kind of (repeated) whitespace) because that's usually what people want. If you need " Foo Bar" to become ("", "Foo", "", "Bar"), use split / /.)
Solution #1 simply nests the syntactic structures: You have a list slice (...)[...] inside a function call say(...). Solution #2 (ab)uses the unary + operator, which is a no-op, but syntactically separates say from (, thus preventing ( from being parsed as the start of an argument list.
But if you only want to extract the first "word" (chunk of non-whitespace) from a string, you could also use say "Foo Bar" =~ /(\S+)/.
Dumb Perl question, because I'm insufficiently caffeinated, the answer isn't coming to me and my DDG-fu is failing me. Given the Perl one-liner that prints "Foo":
```
perl -E 'my @a = (split / /, "Foo Bar"); say $a[0]'
# Foo
```
How do I rewrite it so that an intermediate variable is not required? Doing `say ( ... )[0]` won't work, because `()` controls precedence, it doesn't construct an array. Can't seem to make it work I'm annoyed. 
Why isn’t #Perl popular anymore? It’s got plenty of libraries.
Perl-Guru Matt Trout ist mit 42 Jahren gestorben
Der Mitautor des Webframeworks Catalyst Matt S Trout war für seine humorvollen Vorträge bekannt, er stieß aber auch einige vor den Kopf.
Perl Developer, New Jersey (TEKsystems)
Posted on 2025-07-14
https://jobs.perl.org/job/22046
#Perl
@philsplace @glennf @sixcolors But...because I'm a Perl guy, I stuck that in a script with backticks (a la: " my $status = ``)...then promptly ignore the $status, and end the script knowing that during the next crontab run rsync will fix it it there was an error! 
print "\nTransferring iCloud info from mac at $ip...";
my $status = `/volume2/\@appstore/synocli-net/bin/rsync [...]`;
print "\nResult:\n$status\n\nDone!\n";
Hah! #Perl FTW!
