comment on

I recommend reading the traits paper (where ever it is). It gives specific solutions to all the problems you mentioned (with the exception of comparability).

The solutions are along the lines of: "automatically do the right thing if unambiguous, otherwise the using class must resolve the problem". Eg. namespace clashes must be manually resolved (aliasing at import or using fully qualified names).

The article is also clearly disentangles some problems with traditional OO concepts and shows some non-obvious benefits of their approach. Eg simpler method search, class flattening. The presence of MI in perl means we don't automatically get all the benefits but can opt in. TIMTOWTDI

Brad

In reply to Re: Open to debate on mixins and traits. by bsb
in thread Open to debate on mixins and traits. by BrowserUk

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


There's more than one way to do things
	PerlMonks