From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.5-pre1 (2020-06-20) on ip-172-31-74-118.ec2.internal X-Spam-Level: X-Spam-Status: No, score=-1.9 required=3.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.5-pre1 Date: 19 Sep 91 15:47:29 GMT From: swrinde!zaphod.mps.ohio-state.edu!caen!uvaarpa!software.org!blakemor@gate ch.edu (Alex Blakemore) Subject: Re: VAX Ada question. Message-ID: <1991Sep19.154729.10604@software.org> List-Id: >In article <1991Sep18.043715.13529@ennews.eas.asu.edu> yhartojo@enuxha.eas.asu .edu (Francis Hartojo) writes: >> how do you handle command line parameters in VAX Ada? In article <4590@kluge.fiu.edu> mackey@scs.fiu.edu writes: > use VMS RTL_Routines LIB$ LIB$GET_FOREIGN a better way (at least if you want to look and feel like a VAX command) is to use the VMS command line interface routines (CLI). This allows you to define you command line syntax/defaults and rules about which qualifiers go with others etc in a text file instead of your program. you get default VMS behavior regarding abbreviations - prompting for missing params etc, your application looks just like it came from DEC. (foreign commands look just like that "foreign" to the VMS environment) VMS Ada provides a package called CLI which serves as an Ada interface to the CLI routines (use acs extract source to see it) its in every Ada library (not sublibrary) the spec isnt terribly readable, you probably should read the manual. the name of the manual you want is the VMS Command Definition Utility Manual. -- --------------------------------------------------------------------- Alex Blakemore blakemore@software.org (703) 742-7125 Software Productivity Consortium 2214 Rock Hill Rd, Herndon VA 22070