=================================================================== RCS file: /cvs/todotxt/Text-Todo/lib/Text/Todo.pm,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- todotxt/Text-Todo/lib/Text/Todo.pm 2010/01/06 19:54:56 1.3 +++ todotxt/Text-Todo/lib/Text/Todo.pm 2010/01/06 20:07:16 1.4 @@ -1,6 +1,6 @@ package Text::Todo; -# $RedRiver: Todo.pm,v 1.2 2009/07/10 22:26:14 andrew Exp $ +# $RedRiver: Todo.pm,v 1.3 2010/01/06 19:54:56 andrew Exp $ use warnings; use strict; @@ -120,39 +120,19 @@ =head1 NAME -Text::Todo - [One line description of module's purpose here] +Text::Todo - Perl interface to todo_txt files -=head1 VERSION - -This document describes Text::Todo version 0.0.1 - - =head1 SYNOPSIS use Text::Todo; -=for author to fill in: - Brief code example(s) here showing commonest usage(s). - This section will be as far as many users bother reading - so make it as educational and exeplary as possible. - - =head1 DESCRIPTION -=for author to fill in: - Write a full description of the module and its features here. - Use subsections (=head2, =head3) as appropriate. +For more information see L - =head1 INTERFACE -=for author to fill in: - Write a separate section listing the public components of the modules - interface. These normally consist of either subroutines that may be - exported, or methods that may be called on objects belonging to the - classes provided by the module. - =head2 new =head2 load @@ -190,16 +170,11 @@ =head1 CONFIGURATION AND ENVIRONMENT -=for author to fill in: - A full explanation of any configuration system(s) used by the - module, including the names and locations of any configuration - files, and the meaning of any environment variables or properties - that can be set. These descriptions must also include details of any - configuration language used. - Text::Todo requires no configuration files or environment variables. +Someday it should be able to read and use the todo.sh config file. + =head1 DEPENDENCIES =for author to fill in: @@ -213,26 +188,10 @@ =head1 INCOMPATIBILITIES -=for author to fill in: - A list of any modules that this module cannot be used in conjunction - with. This may be due to name conflicts in the interface, or - competition for system or program resources, or due to internal - limitations of Perl (for example, many modules that use source code - filters are mutually incompatible). - None reported. =head1 BUGS AND LIMITATIONS - -=for author to fill in: - A list of known problems with the module, together with some - indication Whether they are likely to be fixed in an upcoming - release. Also a list of restrictions on the features the module - does provide: data types that cannot be handled, performance issues - and the circumstances in which they may arise, practical - limitations on the size of data sets, special cases that are not - (yet) handled, etc. No bugs have been reported.