summaryrefslogtreecommitdiff
path: root/lib/Data/MultiValued.pm
diff options
context:
space:
mode:
Diffstat (limited to 'lib/Data/MultiValued.pm')
-rw-r--r--lib/Data/MultiValued.pm12
1 files changed, 7 insertions, 5 deletions
diff --git a/lib/Data/MultiValued.pm b/lib/Data/MultiValued.pm
index 9a92ec2..d4c2014 100644
--- a/lib/Data/MultiValued.pm
+++ b/lib/Data/MultiValued.pm
@@ -1,6 +1,6 @@
package Data::MultiValued;
{
- $Data::MultiValued::VERSION = '0.0.1_2';
+ $Data::MultiValued::VERSION = '0.0.1_3';
}
{
$Data::MultiValued::DIST = 'Data-MultiValued';
@@ -17,13 +17,15 @@ warn "Don't use this module directly, use Data::MultiValued::Tags or Data::Multi
__END__
=pod
+=encoding utf-8
+
=head1 NAME
Data::MultiValued - store tag- and range-dependant data in a scalar or Moose attribute
=head1 VERSION
-version 0.0.1_2
+version 0.0.1_3
=head1 SYNOPSIS
@@ -66,17 +68,17 @@ module. Why use these?
=over 4
-=item *
+*
they are optimised for serialisation, see
L<Data::MultiValued::UglySerializationHelperRole> and F<t/json.t>.
-=item *
+*
you get accessors generated for your Moose attributes just by setting
a trait
-=item *
+*
tags and ranges interact in sensible ways, including clearing ranges