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
Message-ID: <0F9F4B0DB88BD21182C20008C70922EADEF9C8@corp-exc5.ctron.com>
From: "Thomas, Mike" <mthomas AT cabletron DOT com>
To: cygwin-developers AT sourceware DOT cygnus DOT com
Subject: RE: Environment Variables
Date: Mon, 7 Jun 1999 16:01:30 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="windows-1252"

Ok it is still the same as in b18, this breaks us, we rely on environment
variables to remain in the case they began in.

Is this something we can suggest in some way to be added in a future rev?

Mike

PS I've been on this mailing list and quite since just after b18 :)
   Mainly because we are still using a heavily modified b18, mostly bug
fixes
   that have been addressed in b20, except the environment..

-----Original Message-----
From: Chris Faylor [mailto:cgf AT cygnus DOT com]
Sent: Monday, June 07, 1999 1:19 PM
To: Thomas, Mike
Cc: cygwin-developers AT sourceware DOT cygnus DOT com
Subject: Re: Environment Variables


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