Hmm, this seems to have stirred up a hornets' nest, sorry. Let me try to pull
together a few threads.
doy, what *would* you name Moose::Role::Matcher if you were to release it today?
Dave Rolsky you said, 'there's multiple role systems on CPAN, so Role !=
Moose'. so, might we distinguish it by
mo wrote:
The question is, how would someone name his dist who wants to release a
version of FSA::Role, which uses Role::Basic as Role framework?
I think we need something like Any::Role :-)
So that implies FSA::Role::Moose for my module, which I don't think would
satisfy hdp.
If there is
Sorry Dave, I read the pod, not the code, to come to that conclusion. :(
From your own example however, it seems you are happy with 'Role' appearing in
the namespace?
For what it is worth, I am now almost certain the name for my module will be.
FSA::Engine 'A Moose Role to convert an object
From: Dave Rolsky [mailto:auta...@urth.org]
For what it is worth, I am now almost certain the name for my module will be.
FSA::Engine 'A Moose Role to convert an object into a Finite State Machine'
I think that's best.
[Ian replied.]
Finally! :)
Thanks everyone for your very helpful
I have written a new module along the lines of FSA::Rules, only as a Moose Role.
Is it convention that Moose Roles are in the MooseX::Role namespace so I would
call the module MooseX::Role::FSA::Simple, or can I call it MooseX::FSA::Simple?
Regards
Ian
--
This e-mail (including any
