nu.kanga.list.mud-dev

15789: RE: [MUD-Dev] (no subject)

> -----Original Message-----
> From: mud-dev-admin@kanga.nu
> [mailto:mud-dev-admin@kanga.nu]On Behalf Of
> John Buehler
> Sent: Monday, November 20, 2000 10:03 PM
> To: MUD-Dev
> Subject: Re: [MUD-Dev] (no subject)
>
> >Essentially, by inheriting, you're assuming that one of
> the parent objects
> >will take full responsibility for the behaviour - one
> parent or another
> will
> >win out wrt: what attributes are inherited, where they
> clash.  If you're
> >componentising, you can list all the different values for
> the different
> >attributes (in essence), and write something to control that.
>
> But in an inheritance system, the parent and child classes
> cooperate in
> providing behavior.  Parent classes can provide utility
> methods that child
> classes can employ, child classes can ignore the parent
> implementation, or
> incorporate the parent implementation into their own behavior.

It seems like the value of components is that it forces you to be
strict and define your relationships clearly and cleanly, while
inheritance allows a programmer to just run with the inheritance and
do whatever, dealing with conflicts when they are a problem.  Or put
differently, components allows the diligent programmer to write tight,
clean code, while inheritance allows a looser mechanism for building
out the codebase.

-j

--
Joe Andrieu
Realtime Drama

joe@andrieu.net
+1 (925) 973-0765



_______________________________________________
MUD-Dev mailing list
MUD-Dev@kanga.nu
https://www.kanga.nu/lists/listinfo/mud-dev