Christoph Otto wrote:
If those are your thoughts on the subject, then it seems to make sense
to add the pdd format test to make test. The attached patch does this.
I'll apply it and mark this ticket as resolved before the next
#parrotsketch unless there are any objections.
Excellent idea.
On Mon Sep 08 00:01:08 2008, [EMAIL PROTECTED] wrote:
Christoph Otto wrote:
If those are your thoughts on the subject, then it seems to make sense
to add the pdd format test to make test. The attached patch does this.
I'll apply it and mark this ticket as resolved before the next
On Mon Sep 08 00:12:44 2008, cotto wrote:
On Mon Sep 08 00:01:08 2008, [EMAIL PROTECTED] wrote:
Christoph Otto wrote:
If those are your thoughts on the subject, then it seems to make
sense
to add the pdd format test to make test. The attached patch does
this.
I'll apply it and
James Keenan via RT wrote:
The PDDs in docs/pdds/ are now in substantial compliance with the coding
standard, those in docs/pdds/draft/ much less so. I'll leave this
ticket open, but it's the sort of thing that only needs some cage
cleaning attention every month or so.
The non-draft PDDs are
Christoph Otto wrote:
The non-draft PDDs are all passing t/codingstd/pdd_format.t as of
r30810, but two of the draft PDDs aren't. Since they're still drafts
and as such are very likely to change, it doesn't seem worthwhile to
bring them into compliance or to have a test depend on them.
I
Allison Randal via RT wrote:
Christoph Otto wrote:
The non-draft PDDs are all passing t/codingstd/pdd_format.t as of
r30810, but two of the draft PDDs aren't. Since they're still drafts
and as such are very likely to change, it doesn't seem worthwhile to
bring them into compliance or to have
On Thu Apr 03 12:17:32 2008, [EMAIL PROTECTED] wrote:
I began working on this today and noticed that many PDDs lack a SYNOPSIS
section -- and they do quite well without it.
I recommend relaxing the requirements in docs/pdds/pdd00_pdd.pod and
t/codingstd/pdd_format.t that each doc have
The PDDs in docs/pdds/ are now in substantial compliance with the coding
standard, those in docs/pdds/draft/ much less so. I'll leave this
ticket open, but it's the sort of thing that only needs some cage
cleaning attention every month or so.
I began working on this today and noticed that many PDDs lack a SYNOPSIS
section -- and they do quite well without it.
I recommend relaxing the requirements in docs/pdds/pdd00_pdd.pod and
t/codingstd/pdd_format.t that each doc have SYNOPSIS section.
All opposed say Nay! within next 24 hours!
Did more work on this tonight. This is a test that, in a certain sense,
will probably never pass completely because there will always be oddball
lines that have to exceed 78 characters. So it will probably never go
into 'make test'.
It is interesting to note that there are extensive stretches
10 matches
Mail list logo
