From: Radical DOT NetSurfer AT delorie DOT com
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Possible bug
Date: Sun, 23 Sep 2001 18:20:40 -0400
Organization: Posted via Supernews, http://www.supernews.com
Message-ID: <jonsqtcta5q49o8eld6b6rbaithusd38k9@4ax.com>
References: <004601c142e7$6f0a2920$323647a1 AT robert> <1pkoqt4ocnvr400nklea28vr51no8tkbsh AT 4ax DOT com> <9oi2nc$1jc$1 AT barcode DOT tesco DOT net> <o6bqqt8gaki7361smv823to2kbd8ls11il AT 4ax DOT com> <1001244576 DOT 694282 AT queeg DOT ludd DOT luth DOT se>
X-Newsreader: Forte Agent 1.8/32.548
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Complaints-To: newsabuse AT supernews DOT com
Lines: 53
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

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

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

I would recommend simply testing any code where these
issues are vital to the operation of any DJGPP program.

(place some printf's, or
 fprintf(stderr,"lets see whats happening here...");
type statements in your program.
If you are satisfied recognizing character-types is working,
or conversion is working, then don't worry!

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.
The light will dawn.

//enough on this topic//

//RadSurfer//

On Sun, 23 Sep 2001 11:29:39 +0000 (UTC), Martin Str|mberg
<ams AT father DOT ludd DOT luth DOT se> wrote:

>Radical wrote:
>: MANY USERS to this very day, Email me (radsmail AT juno DOT com)
>: asking me what I've done to fix problems encountered with
>: "unusual" (to say the least) reaction to DJGPP's strupr/strlwr,
>: toupper/tolower, (and for sake of consistancy) isupper/islower,
>: routines.
>
>: IT WAS A ROUTINE TO FILTER AND RENAME file names
>: from web-site (and usenet) downloads, that contained
>: "freaky" foreign and just dump-a** characters.
>
>: I would suggest this if you want to understand this picture
>: (mind you this was in DJ 2.01/GCC 2.81)
>
>Is the problem still present in 2.03?
>
>
>Right,
>
>						MartinS