From: "Trickey, Howard W (Howard)" <trickey@lucent.com>
To: "'9fans@cse.psu.edu'" <9fans@cse.psu.edu>
Subject: RE: [9fans] bsearch ?
Date: Mon, 30 Jun 2003 10:15:43 -0400 [thread overview]
Message-ID: <D691F041928C1049808A0670D2252BE00428B30C@nj9620exch001u.mh.lucent.com> (raw)
> bsearch(2) is not in libc.
>
> I am sure it will not be for a good reason, but why?
> qsort is there so why not its friend?
bsearch was not in the standard C library in our research Unix;
it must have been added to the standard by someone outside
the Labs. So since we weren't using it, noone felt the need
to put it into the Plan 9 libc.
When I did APE, I needed to do a bsearch, so there is one
in /sys/src/ape/lib/ap/gen/bsearch.c, pretty much isomorphic
to the one just posted by Dan Cross.
- Howard
next reply other threads:[~2003-06-30 14:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-30 14:15 Trickey, Howard W (Howard) [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-30 11:02 steve.simon
2003-06-30 13:57 ` Dan Cross
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=D691F041928C1049808A0670D2252BE00428B30C@nj9620exch001u.mh.lucent.com \
--to=trickey@lucent.com \
--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).