[MUD-Dev] Re: DevMUD: Inheritable modules

James Wilson jwilson at rochester.rr.com
Thu Oct 29 21:00:20 New Zealand Daylight Time 1998

On Thu, 29 Oct 1998, Jon Leonard wrote:
>On Thu, Oct 29, 1998 at 06:53:29PM +0100, The Arrow wrote:

>> It was something like this I thought of when I wrote the mail.
>> The problem with interface inheritance, is how to export the interface.
>> If the modules is written in C++ and we are using external inheritance
>> (as described by Nicklas) the subclassing should be pretty simple.  But how
>> should the driver know what interface (and module) to use runtime?
>My current thoughts on this:
>I don't want to use C++, because it doesn't have the object model I want.

can you elaborate?

>An interface should have a name, and an array of function structures
>like those exported by modules, except without the function pointers.
>We should have a source verifier that checks that the claimed interface
>(name-mangled version of the function, or whatever) matches the prototype
>of the function pointer.
>There should be a separate collection of defined interfaces, so a module
>can just say "I implement interface X" (this can be verified, of course)
>This database of interfaces shouldn't be monolithic -- I don't want to have
>to know about all interfaces that someone else might define.
>Explicit interfaces shouldn't be needed to make runnable MUDs, just
>helpful in configuring them.

did you see my proposal for how this could be done very easily in C++? the
mapping is pretty straightforward.


More information about the MUD-Dev mailing list