Checking in changes prior to tagging of version 0.02.

Changelog diff is:

diff --git a/Changes b/Changes
index cccc82f..9cf7cf4 100644
--- a/Changes
+++ b/Changes
@@ -1,4 +1,9 @@
 Revision history for Perl extension Data::Section::Simple

+0.02  Thu Mar 18 15:14:44 PDT 2010
+        - Added a warning document about __DATA__ appearing elsewhere (rjbs)
+        - Fixed a bug installing via cpanm often fails because fileno $d
+          could be 0 when STDIN is closed (reported by rjbs)
+
 0.01  Thu Mar 18 01:06:44 2010
         - original version

Changes

@@ -1,4 +1,9 @@
 Revision history for Perl extension Data::Section::Simple
 
+0.02  Thu Mar 18 15:14:44 PDT 2010
+        - Added a warning document about __DATA__ appearing elsewhere (rjbs)
+        - Fixed a bug installing via cpanm often fails because fileno $d
+          could be 0 when STDIN is closed (reported by rjbs)
+
 0.01  Thu Mar 18 01:06:44 2010
         - original version

MANIFEST

@@ -17,6 +17,8 @@ META.yml
 README
 t/00_compile.t
 t/basic.t
+t/data.t
+t/DataInCode.pm
 t/Foo.pm
 t/pkg_oo.t
 xt/pod.t

README

@@ -29,14 +29,27 @@ DESCRIPTION
     section of the file.
 
 LIMITATIONS
-    As the name suggests, it's a very simple version of what Data::Section
-    does. If you want more functionalities such as merging data sections or
-    changing header patterns, use Data::Section instead.
+    As the name suggests, this module is a simpler version of the excellent
+    Data::Section. If you want more functionalities such as merging data
+    sections or changing header patterns, use Data::Section instead.
 
     This module does not implement caching (yet) which means in every
-    "get_data_section" or "get_data_section($name)" seeks and reads the data
-    section every time it's called. If you want to avoid doing so, you
-    should implement caching in your own caller code.
+    "get_data_section" or "get_data_section($name)" this module seeks and
+    re-reads the data section. If you want to avoid doing so for the better
+    performance, you should implement caching in your own caller code.
+
+BUGS
+    If you data section has literal "__DATA__" in the data section, this
+    module might be tricked by that. Although since its pattern match is
+    greedy, "__DATA__" appearing *before* the actual data section (i.e. in
+    the code) might be okay.
+
+    This is by design -- in thoery you can "tell" the DATA handle before
+    reading it, but then reloading the data section of the file (handy for
+    developing inline templates with PSGI web applications) would fail
+    because the pos would be changed.
+
+    If you don't like this design, again, use the superior Data::Section.
 
 AUTHOR
     Tatsuhiko Miyagawa <miyagawa@bulknews.net>

lib/Data/Section/Simple.pm

@@ -2,7 +2,7 @@ package Data::Section::Simple;
 
 use strict;
 use 5.008_001;
-our $VERSION = '0.01';
+our $VERSION = '0.02';
 
 use base qw(Exporter);
 our @EXPORT_OK = qw(get_data_section);