[MUD-Dev] Object and class heirarchies -- are they really necessary?
fibhufky at erols.com
Tue Mar 21 15:52:16 New Zealand Daylight Time 2000
<J C Lawrence wrote>
>I recently went over to chat with the Skotos gang. One of the
>things that came up was the handling of object heirarchies.
>When your entire inheritance tree (from an object's perspective) is
>that you all descend from the same super-class -- how do you handle
>multi-user security and access controls for editing the consituent
>components of that super-class?
Help me understand here. I'm not that big on classes (I prefer my poor old
structs ;) In my system, like you mentioned, all game objects are pretty
much the same, however, I simply use structs. I have one super struct with
substructs (for code legibility and managability). What exactly is the
functional differance? IE, What does using classes and inheritence trees
bring to a mud that using super-structs doesn't?
-Admin: Timeless Journies
-Email: fibhufky at erols.com
MUD-Dev mailing list
MUD-Dev at kanga.nu
More information about the MUD-Dev