You wrote that it doesn't sound like I've used traits before. Did you get that impression because of some misunderstanding on my part? If so, I'd love to have it cleared up.

I got that impression simply from the lack of any discussion of real world usage in your posts here and on use.perl. And from the kinds of questions you were asking.

Don't get me wrong. I do not think it is a bad idea that you are writing this module, I just think that CPAN'ing it is somewhat premature given your lack of working knowledge of Traits.

I'd suggest at least trying it out on one of your existing (real) projects to get a solid feel for how Traits can affect your design (composability wise). First, using what you know of Traits from the theoretical perspective, write yourself some 'Use Cases' for how you would like to apply Traits (that's right, programmer's should write Use Cases for themselves when designing new libraries, modules, methodologies, etc. After all, the programmer is the "user/customer" of such technologies). Then look to reworking an existing project with a non-trivial class/object hierarchy that might benefit from composing with Traits. Let your design be informed by theory, but driven by practice.

In reply to Re: Re: Re: Class::Trait to the CPAN? by Anonymous Monk
in thread Class::Trait to the CPAN? by Ovid

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.