[DGD] Inherits.

[Vladimir I. Lazarenko]

Thursday, March 21, 2002, 5:44:45 AM, you wrote:

EH> changes effective in all others, and that _is_ possible if you stick
EH> to the rules that for instance the kernel-lib suggests to you:
EH>   * Keep inheritables and clonables separated.
EH>   * Do not destruct an object for which clones still exist.
EH> I assume you have something like this:
EH>   * Some useful inheritable object:   /lib/utility.c
EH>   * The actual object you're cloning: /obj/clonable.c
EH> Now, to make changes effective in new and already existing clones, you
EH> would:
EH>   * destruct /lib/utility
EH>   * compile /lib/utility.c
EH>   * compile /obj/clonable.c
EH> That last one will actually _recompile_ /obj/clonable.c, i.e. replace
EH> the existing code for /obj/clonable.c while not keeping the same spot
EH> in the object-table, so all clones now point to the new code.

hmm. let's take my situation as an example.
I have a thingie called channel_d (Melville mudlib).
If i make changes to channel_d and then issue 'update channel_d.c'
my changes are not there.

Am I doing anything wrong?

EH> Hope that helps,
EH> Erwin.

-- 
Best regards,
 Vladimir                            mailto:favorit at wanadoo.nl

_________________________________________________________________
List config page:  http://list.imaginary.com/mailman/listinfo/dgd