[Home] [Groups] - Message: [Prev in Group] [Next in Group]

nu.kanga.list.mud-dev

16567: Re: [MUD-Dev] An Idea... Mud Development Framework

[Full Header] [Plain Text]
From: Bruce <bruce@puremagic.com>
Newsgroups: nu.kanga.list.mud-dev
Date: Tue, 16 Jan 2001 12:19:13 -0700
References: [1] [2] [3] [4] <-newest
Organization: Kanga.Nu
Miroslav Silovic wrote:
> "Jeremy Lowery" <macr0@mindspring.com> writes:
> > Scripts could be written in any language that has
> > an ActiveX Script Server Component Registered on the
> > system.  Such as VBScript, Python, JScript, Perl, and
> > LISP, completely depending on the programmers
> > preference and the Interfaces that Language Components
> > provide .
> 
> The obvious drawback of this approach (apart from being Windows-only,
> you really want CORBA for portability),

You could use something like Mozilla's XPCOM (which already
supports multiple languages through IDL and a lot of blah blah
blah).  This is portable to Windows, various Unix platforms,
MacOS and at one point, to OpenVMS.

> is that you can't export the
> script interface back into the server. You also can't inherit scripted
> objects from the server objects or from other scripts. So it's not a
> seamless relationship, it's merely the ability to reuse the exposed
> interface.

With XPCOM, you can I think.  If you define the interface in IDL,
I believe that you can implement it in either C++ or JavaScript.
(With ActiveState working on providing Perl and Python support. 
It is an interesting thing in Mozilla as the boundary between
what has to be C++ and what can be JS is fairly flexible.  I
don't remember enough about this though to know if it was
entirely seamless, or just fairly flexible.

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