Uniformly-distributed integers can be generated with the
random-mtzig:random! procedure. I do need to make the example
consistent with the API, thanks for pointing that out. Initially, the
procedures in that egg were not reentrant, and the state was global. I
forgot to update the example when
On 10/29/07, Ivan Raikov [EMAIL PROTECTED] wrote:
What platform is this on?
cygwin
Instead of commenting out the typedefs,
could you please rename all the type definitions in randmtzig.c and
random-mtzig.scm as follows:
Original:
typedef signed char int8_t;
...
Modified:
typedef
What platform is this on? Instead of commenting out the typedefs,
could you please rename all the type definitions in randmtzig.c and
random-mtzig.scm as follows:
Original:
typedef signed char int8_t;
...
Modified:
typedef signed char randmtzig_int8_t;
...
This should avoid all collisions
On 10/29/07, Ivan Raikov [EMAIL PROTECTED] wrote:
Uniformly-distributed integers can be generated with the
random-mtzig:random! procedure.
procedure: random-mtzig:random! :: STATE - INTEGER
Returns a random integer value between 0 and the largest
machine-representable unsigned integer on the
Ok, I'm getting build problems between data definitions in stdint.h
and some of the source code in random-mtzig
Here was the first error I got:
downloading random-mtzig.egg from
(www.call-with-current-continuation.org eggs 80) .
gunzip -c ../random-mtzig.egg | tar xf -
/usr/local/bin/csc
I want all calls to gcc from Chicken csc to pass
-D__uint32_t_defined -D__int8_t_defined
but I do not know how to modify this compile call so that happens.
please advise:
(compile -O -d2 -X easyffi -s -o random-mtzig.so
,@(if has-exports? '(-check-imports -emit-exports
On Mon, Oct 29, 2007 at 09:04:47AM +0900, Daishi Kato wrote:
Soulds really cool!
One question is why its backend is spiffy, and not http-server.
Is it possible to have an additional backend for http-server?
--daishi
You could certainly write one, but it would be a bit more work because
(define (some-func st)
(lambda (x)
(modulo (random-mtzig:random! st) (abs x
Terrence Brannon [EMAIL PROTECTED] writes:
procedure: random-mtzig:random! :: STATE - INTEGER
Returns a random integer value between 0 and the largest
machine-representable unsigned integer on the
On Mon, Oct 29, 2007 at 05:55:39PM +0900, Daishi Kato wrote:
I see. I didn't realize that part is used.
That said, you are using only a small part of Spiffy, right?
Yeah, currently I am. I'm not yet sure on how to proceed from here.
The amount of stuff used from Spiffy might grow, or it might
On 25 Oct 2007 13:25:53 -0300, Mario Domenech Goulart
[EMAIL PROTECTED] wrote:
Hi Benedikt,
Something weird happened on 2007-10-23. From
http://chicken.wiki.br/automated-builds/2007/10/23/salmonella-report
we can see all the eggs release dates were set to the current date.
It was my
I see. I didn't realize that part is used.
That said, you are using only a small part of Spiffy, right?
I think I should use the Spiffy backend in any case, though.
--daishi
On 10/29/07, Peter Bex [EMAIL PROTECTED] wrote:
On Mon, Oct 29, 2007 at 09:04:47AM +0900, Daishi Kato wrote:
Soulds
On 10/28/07, Terrence Brannon [EMAIL PROTECTED] wrote:
Re: http://galinha.ucpel.tche.br:8080//Unit%20extras#random
Do the numbers from the unit extras random function follow a uniform
distribution?
It uses the standard libc rand() function.
cheers,
felix
On 10/29/07, Terrence Brannon [EMAIL PROTECTED] wrote:
I want all calls to gcc from Chicken csc to pass
-D__uint32_t_defined -D__int8_t_defined
but I do not know how to modify this compile call so that happens.
please advise:
(compile -O -d2 -X easyffi -s -o random-mtzig.so
,@(if
I think it would suffice for daemonize to wrap the call to the daemon's
main procedure in a dynamic-wind block and call the cleanup function
from the exit thunk. Unless the daemon procedure terminates itself with
a low-level _exit or by sending itself a kill signal, the cleanup code
should
Terrence Brannon scripsit:
I dont know why things like SRFI-27 get ratified and have the
inconsistency that Kon discusses in the Issues section of his docs:
http://www.call-with-current-continuation.org/eggs/srfi-27.html
The difference between a final SRFI and a withdrawn SRFI is just
one bit
Mark Fredrickson wrote:
I think it would suffice for daemonize to wrap the call to the daemon's
main procedure in a dynamic-wind block and call the cleanup function
from the exit thunk. Unless the daemon procedure terminates itself with
a low-level _exit or by sending itself a kill signal,
On Oct 29, 2007, at 10:09 AM, John Cowan wrote:
Terrence Brannon scripsit:
I dont know why things like SRFI-27 get ratified and have the
inconsistency that Kon discusses in the Issues section of his docs:
http://www.call-with-current-continuation.org/eggs/srfi-27.html
There is no
I have updated the egg to allow static linking. If you want to build this
yourself, consult the .setup script (numbers egg 1.802). It's not quite
perfect yet, but this should work:
csc myfile.scm -static-extensions -R numbers -X numbers
Do you just want to generate a static executable, or
18 matches
Mail list logo
