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
From:
David Golden
Date:
May 24, 2013 02:34
Subject:
Re: I made t/podcheck.t less sensitive and fixed various pod issues
Message ID:
CAOeq1c_5QygVg-z68mUkNhqnuZDws+s7=hAQAUa0YjLMb+cKxg@mail.gmail.com
On Thu, May 23, 2013 at 9:49 PM, Ricardo Signes
<perl.p5p@rjbs.manxome.org> wrote:
>>   The max line length is increased to 100.  This eliminates dozens of
>>   known issues.
>
> I'm not a fan.  I'd rather fix the issues, and am willing to do so.  Strangely,
> a quick scan suggests that at least some of them aren't even a problem anymore.

IIRC, the calculation assumes something about how many indentation
spaces are added, so a line less than 100 characters long winds up
over 100 after the indent is acounted for.

> I read Pod documentation all the time, almost always in perldoc, in an 80
> column terminal.  I would like to keep things looking good in that format.

I agree.  But I think that sort of clean up should happen in the same
way that people do typo cleanup.  Someone motivated can hunt for long
lines and fix them.

I don't think it needs to be a *porting* check -- it certainly should
be on the Todo list.

> I agree with this sentiment.  I want to be clear, too, that the *other* stuff
> should prevent stuff from landing in blead.  For example, "funny characters"
> without =encoding, duplicate names, etc.

Agreed.

David

--
David Golden <xdg@xdg.me>
Take back your inbox! → http://www.bunchmail.com/
Twitter/IRC: @xdg

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