From: "Sudarshan S Chawathe" <chaw@eip10.org>
To: Per Bothner <per@bothner.com>
Cc: taknamay <taknamay@gmail.com>, kawa@sourceware.org
Subject: Re: SRFI 27
Date: Tue, 22 Oct 2019 12:13:00 -0000 [thread overview]
Message-ID: <28449.1571746394@localhost> (raw)
In-Reply-To: Your message of "Mon, 21 Oct 2019 21:25:25 -0700." <f1fe0c55-4556-010d-528c-d6c8bb499abd@bothner.com>
I have been using a version of SRFI 27 for Kawa that is part of a the
"r7rs-libs" collection of libraries put together by Peter Lane a while
back. On checking the online sources now, though, the material seems to
have fallen off the Web at some point in the past year, so here is an
archive.org link that I found to a version from last year:
https://web.archive.org/web/20180613041335/https://github.com/petercrlane/r7rs-libs
And here is the announcement from a while back:
https://www.lispforum.com/viewtopic.php?t=4635
The implementation is quite simple and builds on java.util.Random, but
not SecureRandom).
That collection (r7rs-libs) has some other useful libraries too, such as
a good portion (maybe all) of SLIB.
Regards,
-chaw
> On 10/21/19 7:11 PM, taknamay wrote:
> > Hi, just wondering if there is a particular reason SRFI 27 has not been
> > implemented yet. If not, I think it would be super-easy given the built-in
> > Java PRNG capabilities. If nobody has time to get around to it, I can
> > submit a patch.
>
> Mainly, because no-one has been sufficiently motivated.
>
> Also, for a good implementation a little research seems in order,
> and it probably makes sense to use the available Java tools,
> such java.util.Random or java.security.SecureRandom.
> --
> --Per Bothner
> per@bothner.com http://per.bothner.com/
next prev parent reply other threads:[~2019-10-22 12:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 2:12 taknamay
2019-10-22 4:25 ` Per Bothner
2019-10-22 12:13 ` Sudarshan S Chawathe [this message]
2019-10-22 13:19 ` Sudarshan S Chawathe
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=28449.1571746394@localhost \
--to=chaw@eip10.org \
--cc=kawa@sourceware.org \
--cc=per@bothner.com \
--cc=taknamay@gmail.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).