Oops, forgot to reply to this, apologies! Thanks for this Bill. More again for me to read up on. Generally I agree that in my experience, composition makes for better maintenance over inheritance. But was curious. Thanks for your thoughts.
iain On Sun, Aug 2, 2020 at 2:36 PM <[email protected]> wrote: > stuff.scm has define-class, define-method, etc. I just use > openlets, where the outer let can be the "class" and each > instance inherits from it. I find this much more flexible > and easier to understand than CLOS-style machinery. I read > somewhere that this is called a "prototype system". I used > CLOS heavily in cmn (back in the 90's), and found that > the hierarchy simply made the code rigid (hard to change) > and opaque (hard to read/debug). A better debugger would have > helped, but this was back in the dark ages. Nowadays > everyone says you should keep your hierarchies as shallow > as possible, which means (does it not?) that no hierarchy > is best :) > >
_______________________________________________ Cmdist mailing list [email protected] https://cm-mail.stanford.edu/mailman/listinfo/cmdist
