From: Andreas Rottmann <a.rottmann@gmx.at>
To: Andy Wingo <wingo@pobox.com>
Cc: Guile Development <guile-devel@gnu.org>
Subject: Re: [PATCH] Allow exposing of random number generator state
Date: Fri, 23 Jul 2010 21:04:39 +0200 [thread overview]
Message-ID: <87aapi2f5k.fsf@delenn.lan> (raw)
In-Reply-To: <m3tynrqx4b.fsf@unquote.localdomain> (Andy Wingo's message of "Thu, 22 Jul 2010 18:50:28 +0200")
Andy Wingo <wingo@pobox.com> writes:
> On Sun 18 Jul 2010 18:01, Andreas Rottmann <a.rottmann@gmx.at> writes:
>
>> Here is a first version of the patch to add an external representation
>> for the RNG state (needed for implementing SRFI 27 "Sources of random
>> bits" in terms of Guile's RNG). I'm not quite sure about the naming of
>> procedures, both one the C and the Scheme side of things -- suggestions
>> highly appreciated!
>
> Great, thanks!
>
> There's something still that doesn't feel quite right about it -- that
> the docs don't define adequately what a seed is, and these 'external'
> values serve a similar purpose -- but oh well. I thought about it for 20
> minutes or so and couldn't think of something better.
>
> I replaced "external" with "datum", in your names. It felt better. Hope
> that's OK.
>
Sure -- seems better to me as well, FWIW.
> In the future would you mind making a few test cases when you submit
> bugfixes or feature patches? It is a pain, but it helps maintain Guile's
> quality through time.
>
OK, I'll add testcases in the future. I've not done so for this and the
other pattch, as the SRFI 27 implementation I'll submit a patch for next
will have tests that (indirectly) excercise the added functionality of
these patches. Testing the features stand-alone would have been better
and yield more self-contained patches, I agree.
Cheers, Rotty
--
Andreas Rottmann -- <http://rotty.yi.org/>
prev parent reply other threads:[~2010-07-23 19:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-18 16:01 [PATCH] Allow exposing of random number generator state Andreas Rottmann
2010-07-22 16:50 ` Andy Wingo
2010-07-23 19:04 ` Andreas Rottmann [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=87aapi2f5k.fsf@delenn.lan \
--to=a.rottmann@gmx.at \
--cc=guile-devel@gnu.org \
--cc=wingo@pobox.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).