develooper Front page | perl.perl5.porters | Postings from May 2013

Re: I made t/podcheck.t less sensitive and fixed various pod issues

Thread Previous | Thread Next
David Golden
May 24, 2013 03:33
Re: I made t/podcheck.t less sensitive and fixed various pod issues
Message ID:
On Thu, May 23, 2013 at 10:44 PM, Karl Williamson
<> wrote:
> I object to this being done without adequate discussion on the list.
> It's not in keeping as to how this project has operated while I've been
> involved, and is contrary to how I would want to have a project operate that
> I contribute to.

Has the code base been made worse?  No.  In fact I fixed a host of
actual known pod issues that had been ignored that no one had bothered
to fix.

This is my beef with podcheck:  It's far to easy to let known issues
grow and be ignored.

If you don't like 100, go fix all the places that are over 100.

Then *GET RID OFF* the known issues file.

Then tighten the limit down to 90.  Then go fix all the places over
90.  Repeat until a point of diminishing returns.

If we *really* thought 80 characters was important, we'd *FIX* the
problem, not use a test that is so easily bypassed.

Karl -- you were responsible for most of the recent commits to
pod/perlebcidic.pod.  Did you fix the many lines over 80?  No, you

I really respect your many contributions to the core, but please walk
the walk before you talk the talk.

Tests that flag things we don't fix aren't constructive.


Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About