@eliasp @ColinTheMathmo BTW #Perl has two well-known tools to encourage and enforce #programming style and best practices, respectively:
• #PerlTidy: https://perltidy.github.io/perltidy
• #PerlCritic: http://perlcritic.com

Your project or team can use their reasonable defaults or further configure them to reflect and maintain the consistent application of your preferences. They also integrate with editors/IDEs, source control management, and author #testing.

@barubary @jens @RL_Dane @stoerdebegga Yes, covered `unless` and line length/formatting via #PerlCritic and #PerlTidy earlier:
• https://social.sdf.org/@mjgardner/109818309913140986
• https://social.sdf.org/@mjgardner/109818639137796370

@jens @RL_Dane @stoerdebegga One reason I choose #Perl is its expressivity without being too “large” of a language. (This last is why I still haven’t wrapped my head around #RakuLang—they threw so much into its core.)

I use #PerlCritic and #PerlTidy to set fairly strict defaults, but both have escape hatches for code islands that need to bend the rules for whatever reason (e.g. better modeling or critical-path performance, or sometimes fencing off legacy code to be brought up to spec later).

@jens @RL_Dane @stoerdebegga #PerlTidy will help you with standardizing on line length and other formatting: https://metacpan.org/dist/Perl-Tidy/view/bin/perltidy

And this core #PerlCritic policy will enforce it: https://metacpan.org/pod/Perl::Critic::Policy::CodeLayout::RequireTidyCode

@jens @RL_Dane @stoerdebegga (I also think every #CPAN distribution should include #perltidy and #perlcritic configs and author tests to encourage consistently-written contributions.)

@chrisjrob @snonux @Perl #PerlTidy and #PerlCritic also help with readable, maintainable, and consistent #Perl code. I like to joke that I don’t have a style, I have a perlcritic policy.

I don’t have discipline, I have a .perltidyrc https://metacpan.org/dist/Perl-Tidy

#Perl #PerlTidy #programming #coding #SoftwareDevelopment

Let me remove your excuses for not using #PerlCritic or #PerlTidy:

1) Use `## no critic` to fence in legacy or experiments in #Perl coding standards from perlcritic https://metacpan.org/dist/Perl-Critic/view/bin/perlcritic#BENDING-THE-RULES

2) Use `#<<<` and `#>>>` to fence in legacy or experiments in code formatting from perltidy https://metacpan.org/dist/Perl-Tidy/view/bin/perltidy#Skipping-Selected-Sections-of-Code

3) Use Test::Perl::Critic::Progressive to gradually enforce coding standards https://metacpan.org/pod/Test::Perl::Critic::Progressive

#programming #coding #testing #SoftwareDevelopment #DevOps

https://mstdn.social/@marick/109389534692696042