[self-interest] Video for interpreter

[Baltasar García Perez-Schofield]

Hi, Farled,

Thanks for the references!
However, my question still stands... is multiple inheritance actually
needed?
This is an interesting question, taking into account inheritance is
implemented as a special case of aggregation in prototype-based programming
languages.

-- baltasar




El jue., 19 nov. 2015 a las 21:21, Faried Nawaz faried at gmail.com
[self-interest] (<self-interest at yahoogroups.com>) escribió:

>
>
> On Thu, Nov 19, 2015 at 5:08 PM, Baltasar García Perez-Schofield
> baltasarq at gmail.com [self-interest] <self-interest at yahoogroups.com>
> wrote:
> >
>
>
> > Many thanks for your interest. Only single inheritance, I'm afraid.
> Multiple inheritance open a box of problems (tie-breaker rule?) that I
> cannot figure out how to solve.
> > I'm also not sure whether it is really needed or not.
> > If I added multiple inheritance, I would transform the parent attribute
> from a reference to a list of references.
>
> You might find these resources helpful:
>
> http://bibliography.selflanguage.org/_static/parents-shared-parts.pdf
> http://sauerbraten.org/lee/ecoop.pdf (not about Self)
>
> http://www.infoq.com/presentations/oop-language-context
> paper:
> https://groups.yahoo.com/neo/groups/self-interest/conversations/messages/3220
>
> This isn't about prototype languages, but I'm sure you'll find it
> interesting, though overkill:
>
>
> http://journal.stuffwithstuff.com/2011/04/21/multimethods-multiple-inheritance-multiawesome/
> https://en.wikipedia.org/wiki/C3_linearization
>
> Faried.
> 
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.selflanguage.org/pipermail/self-interest/attachments/20151120/87b4d405/attachment.html>