From: XXguille AT XXiies DOT XXes (Guillermo Rodriguez Garcia)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Changes to getenv.c
Date: Sun, 13 Jun 1999 16:50:00 GMT
Organization: Telefonica Transmision de Datos
Lines: 27
Message-ID: <37639774.791850@noticias.iies.es>
References: <7ju5dv$3bk2$1 AT newssvr01-int DOT news DOT prodigy DOT com>
NNTP-Posting-Host: iies253.iies.es
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Newsreader: Forte Agent 1.5/32.451
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

El día Sat, 12 Jun 1999 13:25:35 -0400, "Yogesh Sharma"
<SHARMAYOGESH AT prodigy DOT net> escribió:

>Below is the source for getenv.c. I am planning to change the following line
>:
>    while (*ep && *np && *ep == *np && *np != '=')
>
>To
>    while (*ep && *np && toupper(*ep) == toupper(*np) && *np != '=')
>
>Reason for changing this
>
>DOS is not a case sensitive OS, so why don't we convert the environment
>variable and search variable to upper case so that the users may not have
>any problem regarding the case.

It is COMMAND.COM the one that is case insensitive. When you set
environment variables from the command line, COMMAND.COM will
uppercase the variable name; so for the end user, it seems like if var
names were case insensitive, but they are not.

Regards,
GUILLE

----
Guillermo Rodriguez Garcia
XXguille AT XXiies DOT XXes (ya sabes :-)