Path: utzoo!attcan!uunet!crdgw1!crdos1!davidsen
From: davidsen@crdos1.crd.ge.COM (Wm E Davidsen Jr)
Newsgroups: comp.lang.c
Subject: Re: compare strings, strcmp
Keywords: strcmp,strings
Message-ID: <1636@crdos1.crd.ge.COM>
Date: 17 Nov 89 18:21:16 GMT
References: <4463@blake.acs.washington.edu> <11605@smoke.BRL.MIL> <308@charyb.COM> <1632@crdos1.crd.ge.COM> <34344@cornell.UUCP>
Reply-To: davidsen@crdos1.UUCP (bill davidsen)
Organization: GE Corp R&D Center, Schenectady NY
Lines: 17

In article <34344@cornell.UUCP> aitken@cs.cornell.edu (William E. Aitken) writes:

| >| Why the UNSAFE comment?  This looks like utterly standard C to me...
| >
| 	Consider ``StrEq(p++, q++);'' for example.

  I think a number of people, myself included, were looking for
something specific to the macro at hand. Any macro which evaluates
arguments more than once must be used with caution, but then so must
malloc and free, and most of us don't label each use as unsafe.

  I confess that I assumed the object of the warning was a bit more subtle.
-- 
bill davidsen	(davidsen@crdos1.crd.GE.COM -or- uunet!crdgw1!crdos1!davidsen)
"The world is filled with fools. They blindly follow their so-called
'reason' in the face of the church and common sense. Any fool can see
that the world is flat!" - anon