* Message by -Jeronimo Pellegrini- from Sun 2010-04-11:
> On Sun, Apr 11, 2010 at 03:31:54PM +0200, Lasse Kliemann wrote:
> > Use the -p Option to chicken-install in order to direct it to
> > '~/chicken'. However, then the repository will in fact be at
> >
* Message by -Jeronimo Pellegrini- from Sun 2010-04-11:
> $ chicken-install -init ~/chicken/
> copying required files to /home/jeronimo/chicken/ ...
> cp -r /usr/local/lib/chicken/5/setup-api.so /home/jeronimo/chicken/
> cp -r /usr/local/lib/chicken/5/setup-api.import.so /home/jeronimo/chicken
* Message by -Alex Shinn- from Thu 2010-03-18:
> felix winkelmann writes:
>
> > On Wed, Mar 17, 2010 at 1:18 PM, Alex Shinn wrote:
> >>
> >> At 2^26 bits each I would say these are *huge* bit-vectors.
> >>
> >>> (do
> >>> ((i 0 (+ 1 i)))
> >>> ((= i 10))
> >>> (bit-vector-and s1 s2)
> >>>
* Message by -Alex Shinn- from Wed 2010-03-17:
> Lasse Kliemann writes:
>
> > It creates two large bit-vectors, initializes them with
> > random entries, and then performs and, ior, and nand
> > operations (corresponding to intersection, union, and
> > differe
First, thank you everyone for the many answers to my last
question. Here I've got a new issue that I'd like to discuss. It
is about speeding up bit-vector operation using the iset
extension. Consider the program given below. It creates two large
bit-vectors, initializes them with random entries
* Message by -Peter Bex- from Fri 2010-03-12:
> On Fri, Mar 12, 2010 at 07:30:34PM +0100, Lasse Kliemann wrote:
> > Hello Peter, thank you for the answer. I tried it out, but it
> > does not work like the thing I wanted. Here is an example:
> >
> > (receive
>
* Message by -Peter Bex- from Fri 2010-03-12:
> On Fri, Mar 12, 2010 at 05:14:02PM +0100, Lasse Kliemann wrote:
> > How can I start a process and control where it sends its stdout
> > or stderr? I know that I can do:
> >
> > (receive
> >(p-stdout p-stdi
How can I start a process and control where it sends its stdout
or stderr? I know that I can do:
(receive
(p-stdout p-stdin p-pid p-stderr)
(process* command args)
(...))
This gives input and output ports connected to the process. But
how can I express, e.g.: "everything available on p
