Author: jkeenan
Date: Sat Jan 3 19:44:41 2009
New Revision: 34907
Modified:
trunk/t/tools/ops2pm/04-prepare_ops.t
Log:
Change TODO heading in POD to COMMENT and explain why we don't really need to
do what TODO was suggesting.
Modified: trunk/t/tools/ops2pm/04-prepare_ops.t
==============================================================================
--- trunk/t/tools/ops2pm/04-prepare_ops.t (original)
+++ trunk/t/tools/ops2pm/04-prepare_ops.t Sat Jan 3 19:44:41 2009
@@ -256,7 +256,7 @@
F<04-prepare_ops.t> tests whether C<Parrot::Ops2pm::Base::prepare_ops()>
works properly.
-=head1 TODO
+=head1 COMMENT
The following statements and branches in C<prepare_ops()> are as yet uncovered:
@@ -270,6 +270,10 @@
die "$self->{script}: Could not read ops file '$self->{file}'!\n"
unless defined $ops;
+Probably not, because the existence of C<$self->{file} has already been
+checked. But it never hurts to check whether a constructor has returned a
+defined value.
+
=item *
Can I provoke this C<die> message?
@@ -278,6 +282,8 @@
die "$self->{script}: Could not read ops file '$f'!\n"
unless defined $temp_ops;
+Probably not, for same reason as above.
+
=back
=head1 AUTHOR
