From: "Douglas A. Gwyn" <DAGwyn@null.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] plan or side effect
Date: Thu, 7 Mar 2002 09:56:53 +0000 [thread overview]
Message-ID: <3C86B696.E58440C8@null.net> (raw)
In-Reply-To: <20020306102429.671431999B@mail.cse.psu.edu>
geoff@collyer.net wrote:
> #define StrEq(a,b) (*(a)==*(b) && strcmp((a)+1,(b)+1)==0)
> is in general incorrect: *a can equal *b and they can both be NUL
Well, yeah, it was taken from a context where non-null identifiers
were being matched. For more general use one would indeed use your
version..
Note that under reasonable assumptions the macro saves at least a
dozen function calls for each redundant test of byte equality, so
the more conservative version is still a big performance win.
next prev parent reply other threads:[~2002-03-07 9:56 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-06 10:24 geoff
2002-03-07 9:56 ` Douglas A. Gwyn [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-08 19:22 forsyth
2002-03-07 13:45 rob pike
2002-03-07 15:47 ` AMSRL-CI-C
2002-03-05 9:54 Fco.J.Ballesteros
2002-03-06 9:51 ` Thomas Bushnell, BSG
2002-03-06 9:52 ` Douglas A. Gwyn
2002-03-08 9:59 ` ozan s. yigit
2002-03-01 11:35 forsyth
2002-02-28 17:41 David Gordon Hogan
2002-03-01 10:02 ` Thomas Bushnell, BSG
2002-03-01 12:07 ` Boyd Roberts
2002-03-04 10:04 ` Thomas Bushnell, BSG
2002-03-04 17:11 ` Sean Quinlan
2002-03-04 18:23 ` ozan s yigit
2002-03-05 9:41 ` Thomas Bushnell, BSG
2002-03-05 9:56 ` Boyd Roberts
2002-03-05 9:43 ` Boyd Roberts
2002-03-08 17:30 ` Thomas Bushnell, BSG
2002-03-08 18:00 ` Dan Cross
2002-03-11 10:04 ` Ralph Corderoy
2002-03-11 10:04 ` Thomas Bushnell, BSG
2002-03-01 11:57 ` Boyd Roberts
2002-02-27 15:08 presotto
2002-02-27 15:27 ` Sean Quinlan
2002-02-28 9:58 ` Thomas Bushnell, BSG
2002-02-28 12:51 ` Ralph Corderoy
2002-02-28 16:57 ` Thomas Bushnell, BSG
2002-02-28 16:01 ` AMSRL-CI-CN
2002-02-28 16:52 ` Thomas Bushnell, BSG
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3C86B696.E58440C8@null.net \
--to=dagwyn@null.net \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).