Return-Path: Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Delivered-To: mailing list dev@apr.apache.org Received: (qmail 9762 invoked from network); 20 Jan 2001 22:21:45 -0000 Received: from test.webdav.org (HELO kurgan.lyra.org) (198.144.203.199) by h31.sny.collab.net with SMTP; 20 Jan 2001 22:21:45 -0000 Received: (from gstein@localhost) by kurgan.lyra.org (8.9.3/8.9.3) id OAA00719 for dev@apr.apache.org; Sat, 20 Jan 2001 14:21:30 -0800 X-Authentication-Warning: kurgan.lyra.org: gstein set sender to gstein@lyra.org using -f Date: Sat, 20 Jan 2001 14:21:30 -0800 From: Greg Stein To: dev@apr.apache.org Subject: Re: cvs commit: apr/tables apr_tables.c Message-ID: <20010120142130.A704@lyra.org> Mail-Followup-To: dev@apr.apache.org References: <034c01c08302$cecba640$95c0b0d0@roweclan.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from rbb@covalent.net on Sat, Jan 20, 2001 at 09:15:30AM -0800 X-URL: http://www.lyra.org/greg/ X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N It wasn't clear from my checkin message :-) ... I just removed the "btable" option. Binary tables are not useful, given our hash table implementation. What features of a table are you looking for, which hash tables do not provide? Cheers, -g On Sat, Jan 20, 2001 at 09:15:30AM -0800, rbb@covalent.net wrote: > > > > > yes, you *will* use a hash instead. any questions can be directed to Bubba. > > > > > > ????? A hash and a table are two different things and both are > > > useful. How do I insert data into a hash and iterate over it in the exact > > > same order? > > > > apr_table_t is a list, but we don't insert. Hashed tables can't be iterated. > > There needs to be something in between for some classes of data. > > Hmmm... What do you mean we don't insert into a table? There is an > apr_hash_next function to allow us to iterate over the hash table, but of > course the data is now out of order. > > > > I would really have appreciated if this change had been discussed at some > > > point before an entire type was just removed. > > > > Ack, although we aren't using it right -now-, I'm -0.5 on this change > > -0.5 from me too. We may not use it, but this API has been being talked > about since I joined this list over two years ago. By removing it I > believe we have taken a step backwards. :-( > > Ryan > > _______________________________________________________________________________ > Ryan Bloom rbb@apache.org > 406 29th St. > San Francisco, CA 94131 > ------------------------------------------------------------------------------- -- Greg Stein, http://www.lyra.org/