From: Erik Max Francis <max AT alcyone DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: environment variables
Date: Thu, 12 Jun 1997 08:53:57 -0700
Organization: Alcyone Systems
Lines: 19
Message-ID: <33A01B95.61A9E85F@alcyone.com>
References: <01IJYIJ9NKOI8ZPIWK AT NICKEL DOT LAURENTIAN DOT CA> <339F3A64 DOT 5551 AT cs DOT com>
NNTP-Posting-Host: newton.alcyone.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

John M. Aldrich wrote:

> There may well be (in fact, I think there is), but it's a nonstandard
> way to get the environment.  The standard interface is through the
> getenv() and putenv() functions; look them up in the libc docs for more
> info.

If memory servers, Turbo/Borland C++ at one point (and may well still)
used a third argument, char *envp[] (the name is of course irrelevant), to
represent the environment variables.  As you correctly point out, this is
non ANSI C and will not work in other compilers.

-- 
       Erik Max Francis, &tSftDotIotE / email / max AT alcyone DOT com
                     Alcyone Systems /   web / http://www.alcyone.com/max/
San Jose, California, United States /  icbm / 37 20 07 N  121 53 38 W
                                   \
     "Covenants without the sword / are but words."
                                 / Camden