Fold in changes present in released 0.01, but not in repository

META.yml

@@ -1,13 +1,17 @@
 ---
 abstract: 'RFC close address list parsing'
+author:
+  - 'Ruslan Zakirov <ruz@bestpractical.com>'
 build_requires:
   ExtUtils::MakeMaker: 6.36
+  JSON: 0
+  Test::More: 0
 configure_requires:
   ExtUtils::MakeMaker: 6.36
 distribution_type: module
 dynamic_config: 1
 generated_by: 'Module::Install version 1.06'
-license: unknown
+license: perl
 meta-spec:
   url: http://module-build.sourceforge.net/META-spec-v1.4.html
   version: 1.4
@@ -17,4 +21,8 @@ no_index:
   directory:
     - inc
     - t
+requires:
+  Email::Address: 0
+resources:
+  license: http://dev.perl.org/licenses/
 version: 0.02

Makefile.PL

@@ -1,5 +1,11 @@
 use inc::Module::Install;
 all_from 'lib/Email/Address/List.pm';
 readme_from 'lib/Email/Address/List.pm';
+
+requires 'Email::Address';
+
+test_requires 'Test::More';
+test_requires 'JSON';
+
 sign;
 WriteAll;

README

@@ -1,6 +1,38 @@
 NAME
     Email::Address::List - RFC close address list parsing
 
+SYNOPSIS
+        use Email::Address::List;
+
+        my $header = <<'END';
+        Foo Bar <simple@example.com>, (an obsolete comment),,,
+         a group:
+          a . wierd . address @
+          for-real .biz
+         ; invalid thingy, <
+         more@example.com
+         >
+        END
+
+        my @list = Email::Address::List->parse($header);
+        foreach my $e ( @list ) {
+            if ($e->{'type'} eq 'mailbox') {
+                print "an address: ", $e->{'value'}->format ,"\n";
+            }
+            else {
+                print $e->{'type'}, "\n"
+            }
+        }
+
+        # prints:
+        # an address: "Foo Bar" <simple@example.com>
+        # comment
+        # group start
+        # an address: a.wierd.address@forreal.biz
+        # group end
+        # unknown
+        # an address: more@example.com
+
 DESCRIPTION
     Parser for From, To, Cc, Bcc, Reply-To, Sender and previous prefixed
     with Resent- (eg Resent-From) headers.
@@ -10,13 +42,15 @@ REASONING
     mentioned headers and this module is derived work from Email::Address.
 
     However, mentioned headers are structured and contain lists of
-    addresses. Most of the time you want to parse it from start to end
-    keeping every bit even if it's a invalid input.
+    addresses. Most of the time you want to parse such field from start to
+    end keeping everything even if it's an invalid input.
 
 METHODS
   parse
     A class method that takes a header value (w/o name and :) and a set of
-    named options. See below.
+    named options, for example:
+
+        my @list = Email::Address::List->parse( $line, option => 1 );
 
     Returns list of hashes. Each hash at least has 'type' key that describes
     the entry. Types:
@@ -84,3 +118,9 @@ METHODS
         Skip anything that is not recognizable. It still tries to recover as
         described earlier.
 
+AUTHOR
+    Ruslan Zakirov <ruz@bestpractical.com>
+
+LICENSE
+    Under the same terms as Perl itself.
+

lib/Email/Address/List.pm

@@ -9,6 +9,39 @@ use Email::Address;
 
 Email::Address::List - RFC close address list parsing
 
+=head1 SYNOPSIS
+
+    use Email::Address::List;
+
+    my $header = <<'END';
+    Foo Bar <simple@example.com>, (an obsolete comment),,,
+     a group:
+      a . wierd . address @
+      for-real .biz
+     ; invalid thingy, <
+     more@example.com
+     >
+    END
+
+    my @list = Email::Address::List->parse($header);
+    foreach my $e ( @list ) {
+        if ($e->{'type'} eq 'mailbox') {
+            print "an address: ", $e->{'value'}->format ,"\n";
+        }
+        else {
+            print $e->{'type'}, "\n"
+        }
+    }
+
+    # prints:
+    # an address: "Foo Bar" <simple@example.com>
+    # comment
+    # group start
+    # an address: a.wierd.address@forreal.biz
+    # group end
+    # unknown
+    # an address: more@example.com
+
 =head1 DESCRIPTION
 
 Parser for From, To, Cc, Bcc, Reply-To, Sender and
@@ -21,15 +54,18 @@ even mentioned headers and this module is derived work
 from Email::Address.
 
 However, mentioned headers are structured and contain lists
-of addresses. Most of the time you want to parse it from start
-to end keeping every bit even if it's a invalid input.
+of addresses. Most of the time you want to parse such field
+from start to end keeping everything even if it's an invalid
+input.
 
 =head1 METHODS
 
 =head2 parse
 
 A class method that takes a header value (w/o name and :) and
-a set of named options. See below.
+a set of named options, for example:
+
+    my @list = Email::Address::List->parse( $line, option => 1 );
 
 Returns list of hashes. Each hash at least has 'type' key that
 describes the entry. Types:
@@ -352,3 +388,14 @@ sub _process_mailbox {
 }
 
 
+=head1 AUTHOR
+
+Ruslan Zakirov E<lt>ruz@bestpractical.comE<gt>
+
+=head1 LICENSE
+
+Under the same terms as Perl itself.
+
+=cut
+
+1;