package Role::Multiton;
## no critic (RequireUseStrict) - Role::Tiny does strict
use Role::Tiny;
$Role::Multiton::VERSION = '0.2';
use Role::_Multiton ();
sub instance { goto &multiton; }
sub multiton {
my ( $self, @args ) = @_;
my $arg_key = Role::_Multiton::_get_arg_key( \@args );
my $multiton_hr = Role::_Multiton::_get_multiton_lookup_hr($self);
return $multiton_hr->{$arg_key} ||= $self->new(@args);
}
# Need these or YAGNI?
#
# sub get_multiton_lookup_hr { goto &Role::_Multiton::_get_multiton_lookup_hr; }
#
# sub get_my_multiton_key {
# my ($self) = @_;
#
# my $multiton_hr = $self->get_multiton_lookup_hr();
# for my $arg_key ( keys %{ $multiton_hr } ) {
# if ( "$multiton_hr->{$arg_key}" eq "$self" ) {
# return $arg_key;
# }
# }
#
# return;
# }
#
# sub clear_my_multiton_key {
# my ($self) = @_;
#
# my $arg_key = $self->get_multiton_arg_key() || return;
# my $multiton_hr = $self->get_multiton_lookup_hr();
#
# return delete $multiton_hr->{$arg_key};
# }
1;
__END__
=encoding utf-8
=head1 NAME
Role::Multiton - Add a multiton constructor to your class
=head1 VERSION
This document describes Role::Multiton version 0.2
=head1 SYNOPSIS
Object:
package ZeroCool
## no critic (RequireUseStrict) - Moo does strict
use Moo;
with 'Role::Multiton';
…
Code:
use ZeroCool;
my $z3r0 = ZeroCool->new(…); # returns a new object every time, not a multiton (see Role::Multiton::New if you want to do that)
my $z3r1 = ZeroCool->multiton(@args); # returns the same object each time when given the same args
my $z3r2 = ZeroCool->instance(@args); # alias to multiton()
=head1 DESCRIPTION
See L<http://en.wikipedia.org/wiki/Multiton_pattern> for info about multitons.
=head1 INTERFACE
It adds these methods:
=head2 multiton()
Creates a new object initialized with the arguments provided and then returns it.
Subsequent calls to multiton() I<with the same arguments> will return that same object.
You might think of it as an argument based singleton since the arguments are used to make the key in the multiple singleton mapping.
If you’d rather have new() be a multiton use L<Role::Multiton::New> instead.
=head2 instance()
Alias to multiton(). This allows for compatibility with other constructor roles (e.g. L<MooseX::Singleton>, L<Moox::Singleton>).
It is nice because it allows you to switch between what type of instance you get without having to update your code.
For example, if your code does ZeroCool->instance() a million times and you see the need to change from using a singleton to a multiton (or some other instance() defining role), all you have to do is change your class and the consumers will not need to do anything besides update their ZeroCool install (i.e. not update their code in a million places).
Of course, there are also cases when being explicit is important so you’d use multiton().
You can also have both singleton and multiple support (the first one that is with()d will defined instance()):
This will give you multiton(), singleton(), and instance() is a singleton:
with 'Role::Singleton';
with 'Role::Multiton';
This will give you multiton(), singleton(), and instance() is a multiton:
with 'Role::Multiton';
with 'Role::Singleton';
If you’d rather have new() be a multiton use L<Role::Multiton::New> instead.
=head1 DIAGNOSTICS
Throws no warnings or errors of its own.
=head1 CONFIGURATION AND ENVIRONMENT
Role::Multiton requires no configuration files or environment variables.
=head1 DEPENDENCIES
L<Role::Tiny>, L<Role::_Multiton>
=head1 SEE ALSO
L<Role::Multiton::New>, L<Role::Singleton>, L<Role::Singleton::New>
=head1 INCOMPATIBILITIES
None reported.
Definitely works w/ Moo based objects since it uses L<Role::Tiny>.
I’d like to add POD/tests/fixes about what, if anything, needs done to make it with()able for M, Mo, Moose, Mouse, Meese, Meeses, Mooses, etc.
The goal is to be object system agnostic and as minimal as possible.
=head1 BUGS AND LIMITATIONS
No bugs have been reported.
Please report any bugs or feature requests to
C<bug-role-multiton@rt.cpan.org>, or through the web interface at
L<http://rt.cpan.org>.
=head1 AUTHOR
Daniel Muey C<< <http://drmuey.com/cpan_contact.pl> >>
=head1 LICENCE AND COPYRIGHT
Copyright (c) 2013, Daniel Muey C<< <http://drmuey.com/cpan_contact.pl> >>. All rights reserved.
This module is free software; you can redistribute it and/or
modify it under the same terms as Perl itself. See L<perlartistic>.
=head1 DISCLAIMER OF WARRANTY
BECAUSE THIS SOFTWARE IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE SOFTWARE, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE SOFTWARE "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE
ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE SOFTWARE IS WITH
YOU. SHOULD THE SOFTWARE PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL
NECESSARY SERVICING, REPAIR, OR CORRECTION.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE THE SOFTWARE AS PERMITTED BY THE ABOVE LICENCE, BE
LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL,
OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE
THE SOFTWARE (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
FAILURE OF THE SOFTWARE TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
SUCH DAMAGES.