Multi-thread support should be built into UNIVERSAL, instead of being put into threads and threads::share. This would make it much easier for designers to design multi-theaded OO program in a more integrated way;.
Why?
I don't mean to sound facetious, but I don't see any gains in moving thread handling into UNIVERSAL. What behaviour would you like to see? What would be made easier?
As for moving tie to UNIVERSAL I don't understand how this could possibly work. There isn't a single "UNIVERSAL" tie interface - they are separate for scalars, hashes, etc.
Can you give some examples of what you would like to see?
In reply to Re: a strong UNIVERSAL class
by adrianh
in thread a strong UNIVERSAL class
by pg
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |