develooper Front page | perl.perl5.porters | Postings from January 2022

Re: Pre-RFC: Policies

Thread Previous | Thread Next
From:
Darren Duncan
Date:
January 28, 2022 07:37
Subject:
Re: Pre-RFC: Policies
Message ID:
1f396798-5d3d-26c2-07fa-ac1e43c5825f@darrenduncan.net
I don't like this.  It would be better to just use a regular named module that 
does the same thing.  Code like this should always be loaded via the package 
system, rather than hidden locale-specific files.  The only kind of things that 
should be in dotfiles is truly installation-specific stuff and not stuff that is 
logically part of the shared codebase, the shared should be in regular modules, 
and the boilerplate is shared stuff.  -- Darren Duncan

On 2022-01-27 10:22 a.m., Ovid via perl5-porters wrote:
> I want to make it easier to reduce boilerplate.
> 
> One of my clients had a rule that every Perl module has a standard set of boilerplate at the top of every Perl package/script. I changed that to:
> 
>      use Client::Policy;
> 
> That made life much easier. I do this a lot for clients and I don't want to keep doing that. However, there were fiddly bits in writing that module. I'd rather write this:
> 
>      use feature 'policy';
>      policy;
> 
> And that reads a .perlpolicy file and automatically injects its contents into the current code.
> 
> So if .perlpolicy contains this:
> 
>      use v5.26;
>      use warnings;
>      use feature "signatures';
>      no warnings 'experimental::signatures';
>      use Carp qw(carp croak);
> 
> You don't have to write that every time.
> 
> However, we need to consider how the .perlpolicy file is located, and handling the case where you might want different policies for different parts of your code. For example, for Tau Station, we have `Veure::Module`, `Veure::Moose`, and `Veure::Script` depending on our needs. Or if you update Perl, maybe have incremental policies based on the version of Perl?
> 
>      policy; # default
>      policy 'script';
>      policy 'Moose';
> 
> This solves a common problem, but I have not yet thought out all of the implications, so I'd love feedback.

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About