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.
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||