Nexus6! LOL! :D

Thanks for the example. I completely ignored the usage and conceptual power of handles. In fact, handles is a dish I haven't learned to cook. Is there a recipe for it in Moose::Cookbook? Can't find it. Well, in any case the section on handles in the Moose.pm POD is extensive and I'm reading it over as I write this.

BTW, the POD mentions a tree example built with handles that would become a recipe, but in the binary tree recipe handles are not used at all. Maybe this "build your own Nexus6" could become a recipe for it.

around [qw eyes ears nose mouth ] => sub { ... code to make accessors return $self here ... }
I had completely overlooked the existence and possibilities of the array-ref feature in prototyping. That's a great golf tip. Nice. Just one thing, it looks like
    around [qw[eyes ears nose mouth]]
won't work. It should be just a straight array such as:
    around qw[eyes ears nose mouth]

Anyway, your example of using handles for delegation will probably answer most of my chaining needs, but I'd still don't get the subtleties of using handles against using MooseX::CurriedHandles --something I'll look into carefully soon.

Also, defining relationships --from body to eyes and from eyes to body-- seems a little wordy to me. How about this: 

package Body;
use Moose;
has 'eyes' => ( 
    is=> 'rw',
    isa=> 'Eyes',
    metaclass=> 'MooseX::NestedPackage',
    class=> q{
        has 'color'=> (is=> 'rw', default=> 'blue');
    }
);

package main;
my $body=new Body(); ## gets new eyes too
print $body->eyes;   ## and they're blue
$body->eyes(new Eyes(color=>'brown')); 
$body->eyes->color('green');

[download]

Would this syntax be way left field? The extension looks like this (with some quite ugly eval's there). 

package MooseX::NestedPackage;
use Moose;
use Moose::Util;
extends 'Moose::Meta::Attribute';

has 'class' => (is=> 'ro',isa=> 'Str');

after 'attach_to_class' => sub {
    my ($attr, $class) = @_;
    my $name = $attr->name;  # 'eyes'
    my $class_name = $attr->{isa};  # 'Eyes'
    my $class_code = $attr->class;  # all the antlers
    my $parent = $class->{package};  # 'Body'
    my $parent_lc = lc($parent);        #'body'
    $attr->{trigger} = sub { 
        my $self = shift;
        $self->$name->$parent_lc($self);
    };
    my $code = qq{
        package $class_name;
        use Moose;
        $class_code;
        has '$parent_lc' => (is=> 'rw',isa=> '$parent',weak_ref=> 1); 
    };
    eval $code; $@ && die qq{ $@:\n$code };
    ## default is not needed 
    $attr->{default} = sub{ $class_name->new() };
    ## cos defaults should go directly in each nested attribute
    $attr->{lazy} = 0;  ## lazy stopped working outside due to a missi
+ng default
};

[download]

-rodrigo

In reply to Re^3: curried-up moose by rodd
in thread curried-up moose by rodd

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.