Date: Mon, 24 Sep 2001 12:10:08 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Radical DOT NetSurfer AT delorie DOT com
cc: djgpp AT delorie DOT com
Subject: Re: Possible bug
In-Reply-To: <jonsqtcta5q49o8eld6b6rbaithusd38k9@4ax.com>
Message-ID: <Pine.SUN.3.91.1010924120923.25254H-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Sun, 23 Sep 2001 Radical DOT NetSurfer AT delorie DOT com wrote:

> My only advice is use caution when using DJGPP and
> checking for, and changing CASE of a string.
> 
> strupr/strlwr, toupper/tolower,
> and especially,
> isalpha, isupper/islower

There's no need for caution: these functions simply *work* in DJGPP
v2.03.  If you think they don't, please provide a short test program
which demonstrates the problems.

> should have always understood what an ALPHABETIC
> character is, and what most certainly is NOT an alphabetic
> character!

They do!

> try my suggestion of creating a random string of
> chars (all chars 32 to 255 at random, or random lengths)
> and apply the above functions.

I did.  It all worked.  Maybe you have an old version of the library.

Would you please stop frightening users with false assertions?