I've run into trouble because of my problems building master. I'll
have to work around that, so it won't happen tonight.
On Thu, Jan 19, 2012 at 8:54 AM, Noah Lavine wrote:
> Sorry for the delay.
>
> I haven't thought about the PEG stuff in a long time, but looking
> back, I'm pretty sure I didn'
Hello all,
`seed->random-state' is poorly implemented when passed a numeric
argument. It converts the number to a decimal string, and then
`scm_i_init_rstate' takes over and basically adds every 8th byte
together to form the 64-bit internal state.
The problem is that only about 3-bits of entropy
Hello,
As long as we're pinging people for 2.0.5, I don't think this patch
ever got pushed. :-)
I can't build master right now. This is partly my fault for doing so
little sysadmin work that I still have libgc 7.1, but I still think
this one should really, really be in 2.0.5 if the GC changes wil
Replying to myself...
> David Kastrup writes:
>> It does not appear to me that there is any locking that would prevent
>> both ending up with the same random value.
>
> The thread-local 128-bit gensym counters are initialized from
> /dev/urandom. The kernel ensures that each `read' gets freshly
Hi!
Mark H Weaver skribis:
> Anyway, here's the new patch. What do you think? Okay to push? :)
OK to push. Thank you!
Ludo’.
Sorry for the delay.
I haven't thought about the PEG stuff in a long time, but looking
back, I'm pretty sure I didn't change the names yet. I will try to do
it tonight (in GMT-5). I agree, it would be great to have the PEG
stuff finished.
On Thu, Jan 19, 2012 at 4:53 AM, Andy Wingo wrote:
> On W
On Wed 04 Jan 2012 19:12, Andy Wingo writes:
> On Mon 03 Oct 2011 20:21, Noah Lavine writes:
>
>> I hate to make more work for people, but I think the PEG module is
>> almost ready for merging, and could probably be merged if we resolved
>> this names issue. Any other thoughts?
>
> Have you upda
Hello,
I have now pushed an implementation of syntax-local-binding to
stable-2.0, with the following documentation. In the spirit of Eli's
note on Racket's syntax-local-value, it also works with identifiers that
are bound at the module level or the top level. Comments and patches
welcome.
Cheer
On Tue 17 Jan 2012 00:27, Andy Wingo writes:
> TBH I think this is the best thing we can do for local-eval. We
> preserve flexibility for local-eval, make other experiments possible,
> and the local-eval implementation is a bit more perspicacious, as the
> scoping is more lexical (in the same fi
On Sat, Jan 7, 2012 at 10:34 AM, Andy Wingo wrote:
> Greetings, Guilers!
>
> I hope this message finds all of you well: you, and yours, and all the
> beings in your lives. It was really a pleasure to hack with yall last
> year.
>
>
yeah~what a great year for guile!
I agree that Guile-emacs and G
David Kastrup writes:
> It does not appear to me that there is any locking that would prevent
> both ending up with the same random value.
The thread-local 128-bit gensym counters are initialized from
/dev/urandom. The kernel ensures that each `read' gets freshly
generated random bytes, so there
Hi,
Working on porting syntax-parse is a learning experience and I know
understand how it uses
syntax-local-value as a way to lookup a syntax object by joining the wraps
together with the
total wrap at the macro call.
The question is if this really are the total wrap e.g. contains the history
of
12 matches
Mail list logo