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

nu.kanga.list.mud-dev

9965: Re: [MUD-Dev] Virtual machine design

[Full Header] [Plain Text]
From: Jo Dillon <emily@thelonious.new.ox.ac.uk>
Newsgroups: nu.kanga.list.mud-dev
Date: Fri, 16 Apr 1999 17:25:40 +0100
References: [1]
Organization: Kanga.Nu
Shane King (thandor@donut.dhis.org) spake thusly:
> I'm currently working on a mud design, and what I'm really a little
> stuck on is the best way to progress with respect to virtual machine
> design. As I see it, there are four basic options I could go with:
> 
> 1) A java virtual machine, running compiled java (or java-like) code
> 2) Adapt an existing virtual machine from another mud to my needs
> 3) Write my own virtual machine, and make it a target for the egcs
>    compiler, thus allowing it to run byte compiled C/C++ code.
> 4) Write my own virtual machine, and write my own mud language.

  5) Incorporate a general-purpose scripting language - Python's good
for this. Then worry about security ;)
> 
> The java option has some appeal, I must admit. However, sticking to the
> jvm spec is both a plus and minus I guess. At least I have something to
> work from, but it's also rather restrictive. On the up side, there's no
> need to write a compiler. I know some people were talking about using a
> jvm for the devmud vm though, so if they have any thoughts, I'd love to
> hear them.

  I don't think anyone's actually /done/ this.

--
	Jo





_______________________________________________
MUD-Dev maillist  -  MUD-Dev@kanga.nu
http://www.kanga.nu/lists/listinfo/mud-dev