Newsgroups: comp.lang.c
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!sarah!bingnews!bingsuns.cc.binghamton.edu!consp06
From: consp06@bingsuns.cc.binghamton.edu (Robert Konigsberg)
Subject: Re: Efficient STRing CoMPares?
Message-ID: <1991Mar19.222410.1682@bingvaxu.cc.binghamton.edu>
Sender: usenet@bingvaxu.cc.binghamton.edu (Mr UseNet)
Nntp-Posting-Host: bingsunq.pod.binghamton.edu
Reply-To: consp06@bingsuns.cc.binghamton.edu (Robert Konigsberg)
Organization: SUNY Binghamton
References: <1193@caslon.cs.arizona.edu> <15496@smoke.brl.mil> <1991Mar18.174207.7377@bingvaxu.cc.binghamton.edu> <15510@smoke.brl.mil>
Date: Tue, 19 Mar 1991 22:24:10 GMT


In article <15510@smoke.brl.mil>, gwyn@smoke.brl.mil (Doug Gwyn) writes:
|> In article <1991Mar18.174207.7377@bingvaxu.cc.binghamton.edu>
consp06@bingsuns.cc.binghamton.edu (Robert Konigsberg) writes:
|> >Wouldn't it be good then, to include in the macro, something to compare
|> >the actual POINTERS?  If the pointers are the same then the two strings
|> >have no CHOICE but to be equivelant.
|> 
|> Nice try, but in the vast majority of applications the strings being
|> compared, even in cases where they match, are contained in different
|> storage locations.  E.g.
|> 	if ( StrEq( buffer, "EOF" ) ) ...

Yeah, I figured. I just thought I'd give it a try.

			-Rob Konigsberg