"Blech" it is for now.<div><br></div><div>Thinking about it a little more, such subtle considerations go into these decisions.</div><div><br></div><div>Animal::Mammal::Dog::Roles::Pet</div><div><br></div><div>and </div>
<div><br></div><div>Animal::Mammal::Cat::Roles::Pet</div><div><br></div><div>With 25 or so classes in my Eclipse project, let's say I know I need to edit the Dog Pet role. I have trouble quickly distinguishing between the two above in the navigator as they both are named Pet.pm in an open folder named "Role" at the same level. The unsightly naming convention I have helps the files stick out so I can quickly distinguish Dog_PetRole.pm from Cat_PetRole.pm. If I get a lot more roles, maybe I'll end up changing it.<br>
<br></div><div>I'm using the <role>->meta->apply() form, which is pretty ugly no matter how you look at it.</div><div><br></div><div>It definitely won't show up in a CPAN module, and thanks for the feedback</div>
<div><br><div class="gmail_quote">On Mon, Apr 12, 2010 at 11:24 PM, Elliot Shank <span dir="ltr"><<a href="http://chicago.pm">chicago.pm</a>@<a href="http://galumph.com">galumph.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 4/12/10 2:38 PM, Sean Blanton wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Since Moose Roles go into the same package format as regular classes,<br>
how are people organizing them so they can be distinguished from classes<br>
that use them?<br>
<br>
A) Through namespace, as in:<br>
</blockquote></div>
[chop]<div class="im"><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
B) through the package names (I think I'm going to go with this one):<br>
<br>
My::Dog<br>
<br>
My::Dog_GuideRole<br>
<br>
My::Dog_StrayRole<br>
</blockquote>
<br></div>
$rover->does('My::Dog_StrayRole')?<br>
<br>
Blech.<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
C) or you don’t care at all about the fact that a .pm file might be a<br>
Moose role:<br>
<br>
My::Dog<br>
<br>
My::Dog::Guide<br>
<br>
My::Dog::Stray<br>
</blockquote>
<br></div>
I'm for this one.<br>
<br>
See Stevan Little's own opinion on role naming: <a href="http://perl.markmail.org/thread/k77octqrujt5w2pb" target="_blank">http://perl.markmail.org/thread/k77octqrujt5w2pb</a><div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I’d like to hear what others consider when making a decision.<br>
<br>
Does a Moose role even have to be a package?<br>
</blockquote>
<br></div>
It needs a namespace like anything else does.<br>
_______________________________________________<br>
Chicago-talk mailing list<br>
<a href="mailto:Chicago-talk@pm.org" target="_blank">Chicago-talk@pm.org</a><br>
<a href="http://mail.pm.org/mailman/listinfo/chicago-talk" target="_blank">http://mail.pm.org/mailman/listinfo/chicago-talk</a><br>
</blockquote></div><br></div>