Re: Removal of specific Pod::Checker warnings
[email protected] (Shawn H Corey)
| Newsgroups | perl.pod-people |
|---|---|
| Message-ID | <[email protected]> |
On 11/08/11 11:45 AM, Marc Green wrote: > > I agree that a POD checker should report *all* errors/warnings, but is > having an argumentless =item really a warning? > > By Pod::Checker's defintion, a warning indicates bad style, so that > would mean that having an argumentless =item is bad style. Personally, I > don't think it is; I find it a convenient shorthand. Do you disagree? You're correct. Under "Pod Commands", =item is listed as a bare item. I don't know why there is a note for being forgiving for a valid structure, but it's confusing. And, of course, if it's valid, it can't be bad style. -- Just my 0.00000002 million dollars worth, Shawn Confusion is the first step of understanding. Programming is as much about organization and communication as it is about coding. The secret to great software: Fail early & often. Eliminate software piracy: use only FLOSS. "Make something worthwhile." -- Dear Hunter