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

nu.kanga.list.mud-dev

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

[Full Header] [Plain Text]
From: "Jeremy Lowery" <macr0@mindspring.com>
Newsgroups: nu.kanga.list.mud-dev
Date: Sun, 21 Jan 2001 09:54:16 -0600
References: [1] [2] <-newest
Organization: Kanga.Nu
<EdNote: New text moved below quote and quote trimmed>

----- Original Message -----
From: "Bruce" <bruce@puremagic.com>
To: <mud-dev@kanga.nu>
Sent: Thursday, January 18, 2001 11:57 PM
Subject: Re: [MUD-Dev] An Idea... Mud Development Framework


> John Buehler wrote:

>> Just as there are execution interfaces that permit anyone to write
>> their own scripting language, there are authoring interfaces
>> related to scripting that are used by Visual Studio.  Dunno how
>> public they are, but I do know that they're kinda hairy to
>> implement.  Debugging interfaces too.  I don't believe there's
>> anything private about the interfaces that are used to get the
>> Javascript and VBScript languages to work - at any level.

About writing another scripting language.. Isn't there already too
many ways to write a for loop? The reason I think it would be
worthwild to just hook up an interface to a scripting host is because
it's pointless to write another language. There are far too many
as/is. I don't think there would be much, if any, syntax to add to a
language just because you write it for a MUD. Getting away from pure
MS technology, I've been looking at the python API, concidering
imbedding the parser in the mud. Or doing it the other way, extended
python with C++ modules. The main reason scripting seems so appealing
to me is because I'm tired of recompiling everything when I want to
change something. I'm still a bit foggy on what goes where
though. that is in the C++ and in the script.

macr0


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