Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!caip!lll-crg!nike!cit-vax!elroy!smeagol!usc-oberon!tli
From: tli@usc-oberon.UUCP (Tony Li)
Newsgroups: net.decus
Subject: Re: Favorite operating systems query (UNIX vs VMS flaming!!!)
Message-ID: <693@usc-oberon.UUCP>
Date: Thu, 7-Aug-86 02:45:39 EDT
Article-I.D.: usc-ober.693
Posted: Thu Aug  7 02:45:39 1986
Date-Received: Sat, 9-Aug-86 04:15:18 EDT
References: <486@batcomputer.TN.CORNELL.EDU> <1000@ttrdc.UUCP>
Reply-To: tli@usc-oberon.UUCP (Tony Li)
Organization: USC Computing Services, Los Angeles, CA
Lines: 23

In article <859@kbsvax.steinmetz.UUCP> davidsen@kbsvax.UUCP (Davidsen) writes:
[Much stuff deleted.]
    >interface is also clean. To get the values, you only have to issue the 
    >following call.
    >
    >	call dcl$get_value ("input_area", string_variable)
    >
    >and you have it. Easy, no? So, next time, ask someone about a feature you
    		  ^^^^^^^^^ in a word **NO**. To write a program asking
    about the calling sequence instead of typing the command at the prompt
    is not by any stretch of definition "easy".

This is not a program to ask about the calling sequence.  This is a call back 
to DCL to get the value of one of the parameters.  To translate, the above is
roughly eqivalent to:

	strcpy (string_variable, argv[INPUT_AREA]);
-- 
Tony Li ;-)		Usc Computer Science
Uucp: ...!{{decvax,ucbvax}!sdcsvax,hplabs,allegra,trwrb}!sdcrdcf!uscvax!tli
Bitnet: tli@uscvaxq, tli@jaxom, tli@ramoth
Csnet: tli@usc-cse.csnet
Arpa: tli@usc-ecl.arpa