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,54b43bce78b18737
X-Google-Attributes: gid103376,public
From: Keith Thompson <kst@cts.com>
Subject: Re: Dos Environment varables
Date: 1999/05/21
Message-ID: <yec7lq2dor1.fsf@king.cts.com>#1/1
X-Deja-AN: 480697067
References: <7i3stm$o4m$1@news-int.gatech.edu>
X-Complaints-To: usenet@nusku.cts.com
X-Trace: nusku.cts.com 927326835 29139 198.68.168.21 (21 May 1999 22:47:15
 GMT)
Organization: CTS Network Services
NNTP-Posting-Date: 21 May 1999 22:47:15 GMT
Newsgroups: comp.lang.ada
Date: 1999-05-21T22:47:15+00:00
List-Id: <comp.lang.ada>

"Al Lively" <al.lively@business.gatech.edu> writes:
> Can anyone advise how I can access (through Ada code) the contents of local
> environmental variables?

As others have pointed out, some Ada compilers provide routines for
this.

If yours doesn't, or if you want your code to be portable across
compilers, you can probably call the standard C getenv() function.
The C declaration is

     char *getenv(const char *name);

See Interfaces.C (section B.3 in the RM) for information on how to
call C functions from Ada.

-- 
Keith Thompson (The_Other_Keith) kst@cts.com  <http://www.ghoti.net/~kst>
San Diego Supercomputer Center  <http://www.sdsc.edu>                 <*>
Techno-geek.  Mouse bigger than phone.  Bites heads off virtual chickens.