Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com
From: Chris Faylor <cgf AT cygnus DOT com>
Date: Mon, 7 Jun 1999 13:18:38 -0400
To: "Thomas, Mike" <mthomas AT cabletron DOT com>
Cc: cygwin-developers AT sourceware DOT cygnus DOT com
Subject: Re: Environment Variables
Message-ID: <19990607131838.B1738@cygnus.com>
References: <0F9F4B0DB88BD21182C20008C70922EADEF9C4 AT corp-exc5 DOT ctron DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.3i
In-Reply-To: <0F9F4B0DB88BD21182C20008C70922EADEF9C4@corp-exc5.ctron.com>; from Thomas, Mike on Mon, Jun 07, 1999 at 01:08:42PM -0400

On Mon, Jun 07, 1999 at 01:08:42PM -0400, Thomas, Mike wrote:
>I have a quick question...  In b18 environment variables were being changed
>to uppercase before a executing a new process.  In b20 is this still the
>case?  If so is there a mechinisim by which we can change this to not alter
>the environment Maybe a registry entry?

I don't know the answer off the top of my head.  The actual code
involved is is in environ.cc.  I'd suggest that you look there and write
some simple test cases to supply you're own answer.

cgf