Beefy Boxes and Bandwidth Generously Provided by pair Networks
Keep It Simple, Stupid

Re: Hiding trigger code from meta

by stvn (Monsignor)
on Jan 19, 2011 at 19:11 UTC ( #883195=note: print w/replies, xml ) Need Help??

in reply to Hiding trigger code from meta

The standard way is to use an anon-sub, so that is what I would recommend. The only real reason for not using an anon-sub is because you want to be able to use the trigger code in another context, in which case you would want it to show up as a method via meta. Remember that the trigger code is passed $self as the first argument so it works just like a method anyway.

Perhaps you might want to elaborate on the reasoning behind wanting this behavior, it might allow us to give you a better solution.


Replies are listed 'Best First'.
Re^2: Hiding trigger code from meta
by hsmyers (Canon) on Jan 19, 2011 at 21:59 UTC
    Given that trigger is used (at least by me) to verify/limit the value of what we used to call a class variable (do we call them attributes now?) I mostly wanted to avoid the case where the silly but otherwise innocent user of my code calls a function thinking it might be just the thing only to have it; a. not be 'the thing' and b. screw things up. Here is the small class where this came up:
    #!/usr/bin/perl # -- 'Moose' version of use strict; use feature ":5.10"; use Data::Dumper::Simple; our $VERSION = '0.02'; package Piece; use Moose; use Moose::Util::TypeConstraints; my %pieces; enum 'Side' => qw(white black); has 'side' => ( is => 'ro', isa => 'Side', required => 1 ); enum 'Name' => qw(K Q R B N P); has 'name' => ( is => 'ro', isa => 'Name', required => 1 ); enum 'ID' => qw ( WQR WQN WQB WQ WK WKB WKN WKR WQRP WQNP WQBP WQP WKP WKBP WKNP WKRP BQR BQN BQB BQ BK BKB BKN BKR BQRP BQNP BQBP BQP BKP BKBP BKNP BKRP ); has 'id' => ( is => 'ro', isa => 'ID', required => 1, trigger => \&che +ck_id ); sub check_id { my $self = shift; if ( exists( $pieces{ $self->{id} } ) ) { confess "", $self->{id}, " already declared"; } else { $pieces{ $self->{id} }++; } } package Main; use Test::More 'no_plan'; use Test::Fatal; my $wk = Piece->new( side => 'white', name => 'K', id => 'WK' ); isa_ok( $wk, 'Piece' ); isa_ok( $wk, 'Moose::Object' ); is( $wk->side, 'white', '... got the right side for wk' ); is( $wk->name, 'K', '... got the right name for wk' ); is( $wk->id, 'WK', '... got the right id for wk' ); my @methods = Piece->meta->get_method_list(); print Dumper(@methods);
    As you can see an invocation of Piece->check_id() would not be a good thing— although having just said that I suppose I could examine the passed parameters and be able to tell if the call was correct or not. If not complain else do what it was designed to do. At the moment this is a toy so that I can begin to understand Moose with an eye towards converting my CPAN stuff accordingly (21st century and all that…)


    "Never try to teach a pig to wastes your time and it annoys the pig."

      Honestly, I see no reason why you would be worried about someone calling check_id, it will never blow up on them since it will always check the id which is already set. If you want to discourage people from calling it, name it _check_id.

      Also, you shouldn't access the hash directly, you should call $self->id not $self->{id}


Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://883195]
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others drinking their drinks and smoking their pipes about the Monastery: (5)
As of 2018-06-22 01:57 GMT
Find Nodes?
    Voting Booth?
    Should cpanminus be part of the standard Perl release?

    Results (120 votes). Check out past polls.