From: Kevin Ryde <user42@zip.com.au>
Subject: Re: crypt mutex
Date: Sun, 22 Feb 2004 07:50:36 +1000 [thread overview]
Message-ID: <87k72gkspf.fsf@zip.com.au> (raw)
In-Reply-To: <xy71xopktca.fsf@nada.kth.se> (Mikael Djurfeldt's message of "Fri, 20 Feb 2004 22:24:37 -0500")
Mikael Djurfeldt <djurfeldt@nada.kth.se> writes:
>
> Personally, I wouldn't like Guile to have everything thread-safe
> "under the hood". That would be a terrible waste of resources.
I suppose for a start reentrant versions of things can be used when
available,
#if HAVE_CRYPT_R
{
/* FIXME: In glibc 2.3.2, crypt_data is about 128kbytes, maybe we should
think about mallocing it so as not to abuse the stack. */
struct crypt_data data;
data.initialized = 0;
return scm_makfrom0str
(crypt_r (SCM_STRING_CHARS (key), SCM_STRING_CHARS (salt), &data));
}
#else
return scm_makfrom0str
(crypt (SCM_STRING_CHARS (key), SCM_STRING_CHARS (salt)));
#endif
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-02-21 21:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-21 0:32 crypt mutex Kevin Ryde
2004-02-21 3:24 ` Mikael Djurfeldt
2004-02-21 3:26 ` Mikael Djurfeldt
2004-02-23 19:15 ` Marius Vollmer
2004-02-21 21:50 ` Kevin Ryde [this message]
2004-02-23 19:16 ` Marius Vollmer
2004-02-23 19:12 ` Marius Vollmer
2004-02-23 19:46 ` Mikael Djurfeldt
2004-02-23 19:55 ` Mikael Djurfeldt
2004-02-24 1:11 ` Andreas Voegele
2004-02-24 1:22 ` Mikael Djurfeldt
2004-03-20 22:39 ` Marius Vollmer
2004-03-20 22:51 ` Kevin Ryde
2004-07-23 23:53 ` Kevin Ryde
2004-02-23 20:01 ` Mikael Djurfeldt
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=87k72gkspf.fsf@zip.com.au \
--to=user42@zip.com.au \
/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).