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

nu.kanga.list.mud-dev

10259: Re: [MUD-Dev] Text Parsing

[Full Header] [Plain Text]
From: Chris Gray <cg@ami-cg.GraySage.Edmonton.AB.CA>
Newsgroups: nu.kanga.list.mud-dev
Date: Mon, 31 May 1999 07:48:03 -0600
Organization: Kanga.Nu
[Cynbe ru Taren:]

> But let's not do a  blow-by-blow re-enactment of the worst of 50s
> artificial intelligence here, please.

References worth looking at if somewhat is interested, but not
necessarily fully relevant. The goals of a MUD parser are somewhat
different from the goals of a full AI system. A MUD parser needs to have
some degree of efficiency (taking seconds to parse a command is just not
practical), and may well have to deal with words it doesn't know. It just
needs to find a reasonable interpretation for the commands that the
designer has decided it ought to be able to interpret. It doesn't have
to learn from its experience, it doesn't have to build plans to
accomplish things, etc. Things like that would be nice, but they won't
make or break a MUD - they are more on the research fringes for MUDs.
So, I think discussion of simple, practical ways to handle a good
variety of input are quite relevant here. The MUD-Dev archives contain
some earlier discussion on this, as usual.

--
Don't design inefficiency in - it'll happen in the implementation.

Chris Gray     cg@ami-cg.GraySage.Edmonton.AB.CA
               http://www.GraySage.Edmonton.AB.CA/cg/


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