Front page | perl.perl5.porters |
Postings from October 2014
On Wed Oct 15 15:01:47 2014, LeonT wrote: > On Wed, Oct 15, 2014 at 4:11 PM, H.Merijn Brand <h.m.brand@xs4all.nl> wrote: > > > Personally I think that only the first example in a .pod should - if at > > all - state the use strict/use warnings combo. All other code snippets > > and examples can clearly do without. > > > > IMO anything that claims to be a full script should have the full > boilerplate, but snipplets generally don't. > > Leon In order to move this ticket toward resolution, I applied (commit 8bc5de207a4b3d333e9c6535bd21b8f0b1381270) the second patch but with revisions made in light of the discussion in this ticket. 1. This is the first place in pod/perlipc.pod that purports to be a complete program, so per Leon T. I went with Shlomi's "use strict; use warnings;". 2. Went with Aristotle's suggestions re (a) retention of $| rather than STDOUT->autoflush(1); (b) remove superfluous parens around 'qw(catfile)'; (c) print ++$count, "\n";. 3. Did not go with 'say'. Is everyone happy (more or less)? If so, I'll close this ticket by the weekend.. Thank you very much. -- James E Keenan (jkeenan@cpan.org) --- via perlbug: queue: perl5 status: open https://rt.perl.org/Ticket/Display.html?id=122938Thread Previous | Thread Next