On Monday 26 Jul 2010 22:31:24 Ovid wrote:
> I'm thinking about writing a module which is merely a role (Moose::Role)
> which one must consume. While there doesn't appear to be a standard for
> this, I was thinking about trying to set a precedent and use the Does::
> namespace. For example, if you want a upload a role which serializes
> things to YAML, you might call it "Does::Serialize::YAML" to make it clear
> it's a role to be consumed and not a stand-alone package.
>
> Thoughts?
>
I don't see why a role should be under the "Does::" namespace. A better fit
would be to put it under its general purpose instead of outcasting all the
roles to "Does", which is not indicative of their purposes.
Regards,
Shlomi Fish
--
-----------------------------------------------------------------
Shlomi Fish http://www.shlomifish.org/
The Case for File Swapping - http://shlom.in/file-swap
God considered inflicting XSLT as the tenth plague of Egypt, but then
decided against it because he thought it would be too evil.
Please reply to list if it's a mailing list post - http://shlom.in/reply .
