On 2/14/21 3:27 PM, Ralph Mellor wrote:
Undue reliance on inheritance (the primary mechanism used
by classes to organize methods) was recognized in the 1980s
to be a major problem when overused.
Larry understood this. I think it's important that Rakoons know
it too, doubly so if they widely share a summary about OOP as
a Rakoon and/or OOP in Raku. I'm not saying Todd*is* going
to share his keeper widely, but it looked substantive,
If ever someone asked me for it or posts a question on class OOPS.
Someday, maybe in a year of two, I will put them up on line
but I have so very little time at the moment.
and like a
work of love and care,
It was. Thank you for noticing. I have been told
by one individual off line to stop the practice
as it was bragging and showing off and offensive
(paraphrasing him).
so it seemed like he might be intending
to share it beyond this thread.
When I wrote this, it was to help me deal with system
calls and to write my own methods. I had no
idea there was such a thing as "prototype-based"
OOP.
The title of my Keeper is,
"perl6.class.object.method.NativeCall.tutorial.txt"
which I forgot to put on the original posting
I wrote it for absolute beginners frustrated with
all the tutorials that overly complicate things to
the point they become obfuscation. Class OOP in
Raku is just danged easy once you get it explained
right. Like a hash on steroids. I can think of
a couple of programs I have already written that could
have dearly used Class OOP.
And I tried to keep the examples simple (no showing off)
and with a little bit of fun thrown in (BadMath).
I deliberately took out the example on how to
communicate with X11. Way to complicated.
On 2/14/21 9:10 AM, Ralph Mellor wrote:
I elaborate on each of those three points later.
AWESOME! I look forward to it.
