Syntactic Confectionery Delight | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
Re the OO part - there are a few problems with the class idea. Firstly, how do class and package relate? Are they synonymous? Can you have one inside the other? On a somewhat higher level, what if the class construct isn't the best way to do OOP. Some newer languages (Go and Rust) have avoided having a class construct (but still support some flavour of OOP).And going back much further, we find works like the GOF book, which was based around two principles
My own lengthy contemplation has led to a prototype of what such abstractions could look like. Mic provides Interfaces (which support Eiffel-like contracts) as a primary abstraction, and Implementations as a secondary abstraction. I worry that what gets implemented would be "weaker" than what can already be achieved using libraries.In reply to Re: Recap: The Future of Perl 5 (class)
by Arunbear
|
|