PPC0030 (equ) does not have an implementation ready for this release cycle and PPC0031 (eq:u) is controversial.
PPC0027 (any/all) is basically accepted other than needing its feature flag naming figured out.
As an aside regarding PPC0027, we reiterated that we would like use feature ':all' to go away if possible. It was never a good idea anyway, but has become untenable with the introduction of feature flags like indirect and bareword_filehandles, which we expect to have many more of in the future. Since their purpose is to be disabled rather than enabled by default, a simple toggling of all features (on or off) is a nonsensical request.
Do all of your modules have up-to-date contact information? If not, please release new versions with an updated email address in the AUTHOR section.
(And while you're at it, why not add a security policy to your distribution, so that people know how and where to report a security issue with your module.)
If you have a cpan.org email alias, does it forward to the correct email address?
And most importantly, if you are taking time away from maintaining Perl modules, please add ADOPTME or NEEDHELP as co-maintainers to mark your modules as available.
Let me start off by asking the folk on this platform one question. Imagine a scenario that you had lost something important with multiple potential negative consequences. For instance losing a bunch of keys including your car keys, your house keys, your changing room locker keys and a USB stick. What would be the greatest cause for alarm? I suspect that while there may be many possible answers aligned with each individual’s life priorities, the real men in this group know that the most feared is the reaction following the revelation to the wife. For while any calamitous occurrence may be approached objectively, with rationality, reflection and hopefully recovery, this particularly troublesome phase involves heightened emotions, reactivating Mrs Saif’s indelible memories of my many past failings. Objectivity, while desirable in principle, has to deal with such a tainted history.
We agreed on not terrible feature names for PPC0027: keyword_any and keyword_all. These can now be merged.
This led to a brief excursion on the fact that it would be good to have proper iterators as part of the language. But we quickly agreed that the PSC meeting is too small of a margin for that subject.
We talked about the failure of “experimental features”, and possible approaches to remediate that problem. It is going to be difficult to address technically. Philippe pushed for a PPC about the subject.
We took note of the upcoming freeze period and surveyed the changes we think should be merged beforehand. The only thing we weren’t already tracking is the coderef-in-stash optimization, which we decided should be reverted once again and re-attempted earlier in the cycle next time.
Do you want LPW to happen again in 2025? Then you need to make it happen. You need to start thinking about this now. After Lee's closing talk, which detailed how organisation of the 2024 workshop worked and effectively put out a call for organisers for the future, a small number of attendees hinted they would be able to help out in one way or another. For that we are grateful.
However there is no core organising team yet for 2025. Someone, ideally two or three people, need to step up and explicitly say "we are going to organise LPW 2025". If you need help around any of this then we (the 2024 organisers) can guide you. The TPRF have also said they would like to explore how to support LPW 2025 and welcome potential organisers to join the monthly community meeting to discuss this.
Failing that LPW will be going on an indefinite hiatus again.
The Perl Community Conference is a hybrid in-person-and-online event held on December 18th from 10:30a-4:00p CST, Perl's 37th birthday, featuring talks from the world's top Perl programmers and community members. Topics include artificial intelligence, bioinformatics, web applications, chemometrics, genetics, data science, high performance computing, ethics, and much more!
CosmoShop is the largest pure Perl based shop system.
Since 1997, we have been implementing sophisticated and individual eCommerce projects in the B2B sector with our specially developed store software. We are the central point of contact for the entire spectrum.
We spent most of our time on the PPC process, and started by merging Dave Cross’s PR for a static PPC web site. Many thanks to Dave once again.
We discussed revising the PPC process, and started by picking more specific names for the various statuses of a PPC, which we’ll soon apply to the existing PPCs.
There is a “use locale” somewhere in the code you are running.
**Update:** This is specifically in reference to warning about wide characters *“in substitution”*. See also [the follow-up entry](/users/aristotle/2025/03/once-more-subst-widechar-warning.html).
I have just released a trial version of
PPI that includes the
first shot at support for Perl signatures. After installing it, you can access
this feature in the following ways.
For users of perlcritic and other PPI consumers:
include use 5.035; or higher in your code
include use feature 'signatures'; in your code
include a known signatures-enable strictures modules from CPAN in your code,
e.g. Mojolicious::Lite, Modern::Perl
if you enable signatures via a custom strictures module, declare it via %ENV:
PPI_CUSTOM_FEATURE_INCLUDES='{MyStrict=>{signatures=>1}}' perlcritic Work.pm
The Perl Community Conference is a hybrid in-person-and-online event held on December 18th from 10:30a-4:30p CST. Perl's 37th birthday, featuring talks from the world's top Perl programmers and community members. Topics include artificial intelligence, bioinformatics, web applications, chemometrics, genetics, data science, high performance computing, ethics, and much more! Join our mailing list to receive the latest updates!
We have secured a location for anyone looking for a place to participate in person to be. At least 2 Conference talks will be given and streamed LIVE from this location.
See some of the many accomplishments of the Science Perl Committee in just the last year:
At the conclusion of this Conference, we will be announcing our exciting plans for Summer 2025 and future Issues of the Science Perl Journal. Full abstracts for current Issue are now available for free at the site.
We talked a bit about PPC 0025 (Perl version), but didn’t say anything new
Regarding PPC 0030 (new operators) vs PPC 0031 (flags on operators), we continue to think that flags on operators bring more confusion than value (PSC #168). Perl is an operator-rich language, so adding new operators when needed sounds right.
As for the discussion on implicit stringification of references, we think that adding more runtime effects to strict doesn’t really fit. The issue would likely be better addressed with a new warning (and is very similar to the uninitialized warning when dealing with undef).
Someone wanting to make a social media site (such as a Mastodon server & web client for example) will want to allow its users to post URLs, for which previews will be shown in their posts.
These posts will be visited by a UserAgent, but there is the risk that a private IP (disguised as a FQDN hostname that resolves to it) will be in the URL's host, and that might cause security issues.
I could use LWP::ParanoidAgent, but then I'd have to fork a process to make the whole thing async, like a good Mojolicious site will be, and too many processes running can be a problem. Also I'd be missing on the many Roles that exist for Mojo::Useragent.
The sound quality of the recordings is not fantastic. We had some sort of issue that I've tried to fix in post. However, the auto generated captions by YouTube tend to be pretty good these days, so enable those if you have any problems understanding the speaker.
I go into the details a bit more about this in a personal blog post about the event, and how much effort is involved in trying to create the recordings, amongst other things.
Thanks to this year's sponsors, without whom LPW would not have happened:
Just Aristotle and Graham for our first meeting of the new year. Not much progress since the last one due to Christmas, New Year’s, sickness, and other personal circumstances. We discussed our framing of the version bump, the timeline for a decision, and the fact that constraints push us toward a dummy .0 third version component as the simplest way forward.
Spoiler Alert: This weekly challenge deadline is due in a few days from now (on November 3, 2024, at 23:59). This blog post provides some solutions to this challenge. Please don’t read on if you intend to complete the challenge on your own.
Task 1:
You are given a list of dominoes, @dominoes.
Write a script to return the number of dominoes that are similar to any other domino.
$dominoes[i] = [a, b] and $dominoes[j] = [c, d] are same if either (a = c and b = d) or (a = d and b = c).
I was one of the organisers of the London Perl and Raku Workshop 2024, which happened last weekend. I've written about my own personal experience of this conference over on my personal blog.
