Path: utzoo!mnetor!uunet!husc6!think!ames!pasteur!ucbvax!ucdavis!iris!hildum
From: hildum@iris.ucdavis.edu (Eric Hildum)
Newsgroups: comp.os.vms
Subject: Re: Help us defend against VMS!
Message-ID: <1518@ucdavis.ucdavis.edu>
Date: 24 Mar 88 02:41:55 GMT
References: <2814@enea.se> <20597@bu-cs.BU.EDU> <341@wsccs.UUCP> <342@wsccs.UUCP> <5640@swan.ulowell.edu>
Sender: uucp@ucdavis.ucdavis.edu
Reply-To: hildum@iris.UUCP (Eric Hildum)
Organization: U.C. Davis - College of Engineering
Lines: 22

In article <5640@swan.ulowell.edu> arosen@hawk.ulowell.edu (MFHorn) writes:
>
>Which means DCL has to know the syntax of every command on the sytem.  Yeah,
>real modern.  Makes it real easy to add commands to the system, too.
>Especially for users who write their own private little utilities.  Can you
>say search path?
>

You might want to look into this a bit more. To teach DCL a new
command, one uses the command SET COMMAND filename, where the file
contains a description of the command verb, the filename of the image
to be activated, the qualifiers allowed or required, defaults, etc. 
Having added several commands to the system, I can assure you that it
is quite easy.

I am not sure what you mean by "modern."  Why shouldn't your command
table know the syntax of your commands?

				Eric
				dehildum@ucdavis.ucdavis.edu	(Internet)
				dehildum@ucdavis.bitnet	(BITNET)
				ucbvax!ucdavis!dehildum	(uucp)