Not to pick on James here. There are a LOT of files where we put the
name of the file *in* the file; this becomes a maintenance burden,
especially with duplication, refactoring, renaming...
I noticed this when trying to do some cleanup in the t/ directory
some months ago. For example, in the cut at the end,
are NAME & SYNOPSIS necessary here at all? They are just boilerplate
that's going to bitrot; We can write the SYNOPSIS once at a toplevel
doc somewhere. The NAME is just the path; you obviously know the path
if you ran the perldoc to see it.
Any thoughts?
$ head -20 t/oo/composition.t
#!perl
# Copyright (C) 2007, The Perl Foundation.
# $Id: /parrot/offline/t/oo/composition.t 7681
2007-09-06T12:28:44.077679Z coke $
use strict;
use warnings;
use lib qw( . lib ../lib ../../lib );
use Test::More;
use Parrot::Test tests => 10;
=head1 NAME
t/oo/compositon.t - test role composition
=head1 SYNOPSIS
% prove t/oo/compositon.t
=head1 DESCRIPTION
On Oct 6, 2007, at 9:24 PM, [EMAIL PROTECTED] wrote:
/t/configure/039-run_single_step.t
--
Will "Coke" Coleda
[EMAIL PROTECTED]
