From: forsyth@caldo.demon.co.uk forsyth@caldo.demon.co.uk
Subject: [9fans] rsynth, yes enjoyed much
Date: Mon, 26 Apr 1999 18:04:04 +0100 [thread overview]
Message-ID: <19990426170404.JHUESBlaSHO2cwaFTkQQyADCrMNkoTqSTio5qZvZ6Xk@z> (raw)
>>multiple users in any access method. With dbm
>>type routines the system will need file locking, etc.
investigation of dbm/libgdbm was prompted by its limited use
in rsynth, where such things aren't really a problem since
both dictionary and index are essentially static.
on the other hand, the argument was that going to the
effort of disentangling libgdbm's source-level dependence
on a posix environment to be able to use <libc.h>,
in order to link it with rsynth. it has just occurred to
me that i've got another lookup routine that i could
easily use freely instead. i'll change the rsynth port to use it.
in general, though, you're right!
next reply other threads:[~1999-04-26 17:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-26 17:04 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-05-01 13:02 okamoto
1999-04-27 0:54 okamoto
1999-04-26 13:40 G.David
1999-04-26 7:29 okamoto
1999-04-26 6:51 forsyth
1999-04-26 4:20 okamoto
1999-04-25 21:50 Scott
1999-04-25 17:42 Russ
1999-04-25 11:22 forsyth
1999-04-25 7:57 okamoto
1999-04-23 9:53 forsyth
1999-04-23 8:48 okamoto
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=19990426170404.JHUESBlaSHO2cwaFTkQQyADCrMNkoTqSTio5qZvZ6Xk@z \
--to=forsyth@caldo.demon.co.uk \
/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).