=head1 VERSION
-Version 0.02
+Version 0.03
=cut
our $VERSION;
BEGIN {
- $VERSION = '0.02';
+ $VERSION = '0.03';
}
=head1 SYNOPSIS
+ { package Str; }
+
{
- package Str;
+ package My::Types::Str;
- sub TYPEDSCALAR { Some::String::Implementation->new }
+ sub new { bless { }, shift }
+ }
+
+ use Lexical::Types as => sub { 'My::Types::' . $_[0] => 'new' };
+
+ my Str $x; # $x is now a My::Types::Str object
+
+ {
+ package My::Types::Int;
+
+ sub TYPEDSCALAR { bless { }, shift }
}
use Lexical::Types;
- my Str $x; # $x is now a Some::String::Implementation object
+ use constant Int => 'My::Types::Int';
+
+ my Int $y; # $y is now a My::Types::Int object
=head1 DESCRIPTION
-This pragma allows you to hook the execution of typed lexicals declarations (C<my Str $x>).
-In particular, it can be used to automatically tie or bless typed lexicals.
+This pragma allows you to hook the execution of typed lexicals declarations (C<my Str $x>) by calling a configurable method in a configurable package at each run.
+In particular, it can be used to automatically tie or bless typed lexicals whenever they are initialized.
+
+Remind that for C<perl> to be able to parse C<my Str $x>, you need :
+
+=over 4
+
+=item *
+
+either the C<Str> package to be defined ;
+
+=item *
+
+or for C<Str> to be a constant sub returning a valid defined package.
+
+=back
+
+so make sure you follow one of those two strategies to define your types.
-It is B<not> implemented with a source filter.
+This pragma is B<not> implemented with a source filter.
=cut
either an empty list, in which case the current typed lexical definition will be skipped (thus it won't be altered to trigger a run-time hook) ;
- use Lexical::Types as => sub { return $_[0] =~ /Str/ ? () : @_ };
- my Str $x; # nothing special
- my Int $y; # calls Int->TYPEDSCALAR
+ use Lexical::Types as => sub { return $_[0] =~ /Str/ ? @_ : () };
+ my Str $y; # calls Str->TYPEDSCALAR
+ my Int $x; # nothing special
=item *
=back
-Those restrictions apply even if you use the C<'as'> option to redirect to another package, and are unlikely to find a workaround as this happens deep inside the lexer - far from the reach of an extension.
+The restrictions on the type (being either a defined package name or a constant) apply even if you use the C<'as'> option to redirect to another package, and are unlikely to find a workaround as this happens deep inside the lexer - far from the reach of an extension.
Only one mangler or prefix can be in use at the same time in a given scope.