Thanks for the discussion LanX :-) I think that you're looking for something too complicated, and that Roles just do the trick. (i might well be wrong). Here is the Perl code for getting the same behavior as the Ruby code from the slides (it could all be shorter and put in the same file, with MooseX::Declare - but some people might not have it installed):

test.pl

use feature ':5.16';
use strictures;

use Door;
use Moose::Util  qw( apply_all_roles );

my $main_door = Door->new;

# The Door is Closed
$main_door->knock;  # knock knock

# Open it
apply_all_roles($main_door, 'Opened');
$main_door->knock;  # just come on in!

# Close it
apply_all_roles($main_door, 'Closed');
$main_door->knock;  # knock knock

# Bug ??
say 'Why does this not print ??' 
    if $main_door->DOES('Closed');
[download]

Door.pm

package Door;

use Moo;
use feature ':5.16';
use Moose::Util   qw( apply_all_roles );

sub BUILD {
    apply_all_roles($_[0], 'Closed');  
        # default State at construction
}

sub knock {
    say 'DEFECT: a door should never be nor opened nor closed';
        # This method will be overriden by the Roles 
        # (should never be printed)
}

1;
[download]

Closed.pm

package Closed;

use Moose::Role;
use feature ':5.16';

sub knock {
    say 'knock knock';
}

1;
[download]

Opened.pm

package Opened;

use Moose::Role;
use feature ':5.16';

sub knock {
    say 'just come one in!';
}

1;
[download]

Which does what is expected (output written as comments in test.pl).

But it has several problems:

• To check whether a Door is closed or opened, i need to check if the object DOES any of these two Roles. Unfortunately, DOES seems to not work, for a Role instanciated on an object. This might be a bug in Moose::Object::DOES. (see the last line of test.pl)
• When a door is Closed, it is still Opened at the same time. I need to be able to unapply_role(). Which is what they do in the Ruby example with 'unmixin'. And it's my initial question in this thread: how to do it in Perl?

If there were simple solutions to these two problems, then i think we could implement complex State machines with multidimensional states.

There is here someone who asked pretty much the same question as me, with a pretty good example of multidimensional State machine: a warrior who can be turned into a Zombie, poisoned, made stronger, turned into a Chipmunk, or all of these at the same time. The answer to that person's question was an alternative solution with aspects. I would still prefer the solution with Roles, which are more flexible, and in my opinion clearer.

Was that clear? Helpful? Did i miss your point LanX?

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.