From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,560db337e2dbcd3e
X-Google-Attributes: gid103376,public
From: kilgallen@eisner.decus.org (Larry Kilgallen)
Subject: Re: How to pass commandline parameters to a vax vms ada main prog
Date: 1997/01/25
Message-ID: <1997Jan25.131045.1@eisner>#1/1
X-Deja-AN: 212168147
x-nntp-posting-host: eisner.decus.org
references: <32E71F0B.270@dfd.dlr.de> <32E94CAC.4148@lmtas.lmco.com>
x-nntp-posting-user: KILGALLEN
x-trace: 854215855/2886
organization: LJK Software
newsgroups: comp.lang.ada
Date: 1997-01-25T00:00:00+00:00
List-Id: <comp.lang.ada>


In article <32E94CAC.4148@lmtas.lmco.com>, Ken Garlington <GarlingtonKE@lmtas.lmco.com> writes:

> In addition to the Ada advice already posted, don't forget that you
> will need to define your executable as a foreign command; e.g. for
> executable TEST.EXE
> 
> TEST :== $disk:[directory]TEST.EXE
> 
> The dollar sign at the front is important. Then, you should be able to
> execute TEST as a verb:
> 
> $ TEST stuff
> 
> and read/parse "stuff" successfully.

You can get away without defining a symbol if you are willing to do more
typing for each invocation:

	$ MCR disk:[directory]TEST.EXE StUFf

An example of a situation where lots of typing per invocation is when
every invocation will be from a command procedure.  The computer does
not care.

The basic rule about command line parsing in VMS, no matter how you
do it, is that there will be nothing to parse if you use the RUN
command to invoke the program.

Larry Kilgallen