From: "Chris" <nanakos@wired-net.gr>
To: "M.Baris Demiray" <baris@labristeknoloji.com>,
linux-c-programming@vger.kernel.org
Subject: Re: Fw: Array Empty Slots
Date: Tue, 5 Apr 2005 17:25:05 +0300 [thread overview]
Message-ID: <00a301c539eb$43448930$0101010a@dioxide> (raw)
In-Reply-To: 4252C84F.3070600@labristeknoloji.com
Nice try, but this problem has always been a sigificant point for DBMS
applications, web based or not.
Maybe i should better explain you the problem. Suppose that we have this
array below:
array = [ 0,1,2,3,4,5,7,8,9,10];
Which is the quickest way to find the missing sequential number in a sorted
array of a fixed lenght???
next prev parent reply other threads:[~2005-04-05 14:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-05 13:09 Fw: Array Empty Slots Chris
2005-04-05 16:48 ` M.Baris Demiray
[not found] ` <002701c539e8$093d85f0$0101010a@dioxide>
[not found] ` <4252C84F.3070600@labristeknoloji.com>
2005-04-05 14:25 ` Chris [this message]
2005-04-05 16:50 ` Luciano Moreira - igLnx
[not found] ` <32785.62.38.143.174.1112726575.squirrel@webmail.wired-net.gr>
2005-04-05 19:51 ` Luciano Moreira - igLnx
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='00a301c539eb$43448930$0101010a@dioxide' \
--to=nanakos@wired-net.gr \
--cc=baris@labristeknoloji.com \
--cc=linux-c-programming@vger.kernel.org \
/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).