Re: [Chicken-hackers] [C5] About `random` and its future

2017-09-17 Thread John Cowan
On Sun, Sep 17, 2017 at 1:43 PM, lemonboy wrote: AFAICT the `extras` module contains a bunch of useful procedures to get one > started writing so it'd be nice if we could choose and implement a single > PRNG, > taking advantage of the (light) breakage introduced by C5. > Is there anything wrong

Re: [Chicken-hackers] [C5] About `random` and its future

2017-09-17 Thread Jim Ursetto
You could use random-bsd as a drop-in replacement if you want. http://api.call-cc.org/doc/random-bsd > On Sep 17, 2017, at 12:43 PM, lemonboy wrote: > > Hello hackers, > this time there's no patch and no code involved. I recently had some code that > used the `random`/`randomize` duo from the `

[Chicken-hackers] [C5] About `random` and its future

2017-09-17 Thread lemonboy
Hello hackers, this time there's no patch and no code involved. I recently had some code that used the `random`/`randomize` duo from the `extras` module to do some operations on some data. The code came with a modest test suite that worked just fine on my laptop but failed when run on other systems

Re: [Chicken-hackers] [PATCH] Fix #1414 by not mallocing in a signal handler

2017-09-17 Thread Peter Bex
On Sun, Sep 17, 2017 at 05:43:07PM +1200, Evan Hanson wrote: > Hi Peter, > > I've applied this to both branches. Thanks for the explanation, it was > helpful in trying to figure out what will happen when the trace buffer > is filled more quickly than signals arrive. I also had to convince > myself

Re: [Chicken-hackers] [PATCH] Add initial version of (chicken base)

2017-09-17 Thread Peter Bex
On Sun, Sep 17, 2017 at 11:44:09AM +0200, felix.winkelm...@bevuta.com wrote: > > > It should be possible to link with units, but I guess that can be done > > > via "declare". > > > If that is still possible then "require-library" may indeed go. > > > > Yeah, I think that's still possible. > > Wha

Re: [Chicken-hackers] [PATCH] Add initial version of (chicken base)

2017-09-17 Thread felix . winkelmann
> > It has uses - "notice" is different, and can be replaced by a (trivially) > > implemented user-made logging facility. This may sound a bit like > > bikeshedding, > > but we will break a bit of code otherwise. > > Note that the second patch I supplied doesn't remove "notice" or "warning", > it