From: Thien-Thi Nguyen <ttn@gnu.org>
To: Alexandru Cojocaru <xojoc@gmx.com>
Cc: guile-user@gnu.org
Subject: Re: Which hashtable API to use?
Date: Fri, 16 Aug 2013 16:08:26 +0200 [thread overview]
Message-ID: <87ob8xpw2t.fsf@zigzag.favinet> (raw)
In-Reply-To: <520E0F3E.8060509@gmx.com> (Alexandru Cojocaru's message of "Fri, 16 Aug 2013 13:38:38 +0200")
[-- Attachment #1: Type: text/plain, Size: 630 bytes --]
() Alexandru Cojocaru <xojoc@gmx.com>
() Fri, 16 Aug 2013 13:38:38 +0200
currently there are three hashtable APIs [...]
Which one to choose?
It's best to choose what you feel comfortable maintaining.
It's next best to choose what you can write and understand.
After that is cut and paste copying from other people's code.
Worst is abiding blindly by advice in a j.r.hacker posting...
--
Thien-Thi Nguyen
GPG key: 4C807502
(if you're human and you know it)
read my lisp: (responsep (questions 'technical)
(not (via 'mailing-list)))
=> nil
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2013-08-16 14:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-16 11:38 Which hashtable API to use? Alexandru Cojocaru
2013-08-16 12:47 ` Matt Wette
2013-08-16 13:33 ` Alexandru Cojocaru
2013-08-17 0:00 ` Matt Wette
2013-08-16 14:08 ` Thien-Thi Nguyen [this message]
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ob8xpw2t.fsf@zigzag.favinet \
--to=ttn@gnu.org \
--cc=guile-user@gnu.org \
--cc=xojoc@gmx.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).