NetNews Usenet Archive 1993 #3/NN_1993_3.iso/spool/gnu/gcc/help/3005

Internet Message Format | 1993-01-23 | 1.9 KB

Xref: sparky gnu.gcc.help:3005 comp.os.vms:21799
Path: sparky!uunet!elroy.jpl.nasa.gov!nntp-server.caltech.edu!SOL1.GPS.CALTECH.EDU!CARL
From: [e-mail] (Carl J Lydick)
Newsgroups: gnu.gcc.help,comp.os.vms
Subject: Re: problem report of toupper() in GCC 1.42 on VMS
Date: 23 Jan 1993 00:37:57 GMT
Organization: HST Wide Field/Planetary Camera
Lines: 33
Distribution: world
Message-ID: <[e-mail]>
References: <[e-mail]>
Reply-To: [e-mail]
NNTP-Posting-Host: sol1.gps.caltech.edu

In article <[e-mail]>, [e-mail] (Bob Pasker) writes:
=GNU_CC_INCLUDE:[000000]ctype.h has the following utterly useless
=definition of toupper():
=
=    #define toupper(c)      ((c)-'a'+'A')
=
=since there exists a properly functioning routine in the RTL, the
=proper definition is:
=
=    char toupper(char);
=
=or, if you don't like the CALLS, roll yer own #define that makes
=(toupper('A') == toupper('a')) be a true value.
=
=tolower() is similarly brain dead.

It's not totally useless.  It simply must always be used in conjunction with
islower().  E.g.,
    c = islower(c) ? toupper(c) : c;
or
    c = isupper(c) ? tolower(c) : c;

Of course, then you've got to worry about side-effects.  I can't, at the
moment, any way, think of a way to implement toupper() via a macro that doesn't
use its argument at least twice and that has the check for islower() built in.
--------------------------------------------------------------------------------
Carl J Lydick | INTERnet: [e-mail] | NSI/HEPnet: SOL1::CARL

Disclaimer:  Hey, I understand VAXen and VMS.  That's what I get paid for.  My
understanding of astronomy is purely at the amateur level (or below).  So
unless what I'm saying is directly related to VAX/VMS, don't hold me or my
organization responsible for it.  If it IS related to VAX/VMS, you can try to
hold me responsible for it, but my organization had nothing to do with it.