[218] in Coldmud discussion meeting

root meeting help first first in chain previous in chain previous next last

Re: consistency in match_template

daemon@ATHENA.MIT.EDU (Thu Apr 28 20:50:46 1994 )

From: stewarta@netcom.com (Alex Stewart)
To: eostrom@pepperoncini.gac.edu (Erik Ostrom)
Date: Thu, 28 Apr 1994 17:45:55 -0700 (PDT)
Cc: coldstuff@MIT.EDU
In-Reply-To: <9404282120.AA08120@gac.edu> from "Erik Ostrom" at Apr 28, 94 04:20:01 pm

> Imagine if, each time you wanted to do something, you had to stop and
> remember which 4-tuple of quoting semantics the command you're
> thinking of uses.  Staggering.

No, no, no, no, no.  I have never had someone miss my point so completely (and
trust me, Lynx does a lot of it).  I had thought it would be fairly obvious
from everything else I said that this is exactly what I was NOT proposing.
There are two issues here.  One is how user commands should be handled and the
other is how match_template should work.  they are related but they are not the

The command parser would only use one specific set of options for matching all
command templates, but which options are used would be up to the people writing
the DB, not hardcoded into the routine.  In short, make the server as flexible
as possible and leave the actual uses of it up to the people designing the
individual systems.