Sure. Like I said in the original post, the MUD Engine creates a sandbox for
the MUD to run in. This protects the host system, and just makes things easier
to implement within the MUD itself when you have a well-controlled environment.
I want all classes to contain a subset of methods so that the MUD Engine can
track, serialize, and manage them better. Some properties will be as simple as
unique IDs (which I'm currently just using hash_value() of the object), or the
MUD-specific file location of the program, or if the object is tied to a
specific user and the MUD Engine connection object that represents that user.
While I can do all of this in a separate mapping using the MUD Object's unique
ID, I wanted to see how well things would work if it were actually a part of the
MUD Object.
________________________________
From: "Mirar @ Pike importmöte för mailinglistan" <<6341[at]lyskom.lysator.liu.se>>
To: <pike[at]roxen.com>
Sent: Wednesday, September 9, 2009 11:55:02 AM
Subject: Re: Is there anyway to have a class always be inherited from other
objects?
May I ask what problem using a base class solves?
|