Hi,
On May 21, 2013, at 6:56 AM, Alexander Burger a...@software-lab.de wrote:
They talk about task stacks and preserved on this stack. I assume
that these stacks all reside on the single hardware stack, right? So
there is a stack *frame* for each task, and this frame might also be
used to
Hi,
On May 21, 2013, at 7:46 AM, Alexander Burger a...@software-lab.de wrote:
The big question is: Will the system (which system?) do that? If so, how
do other languages implement green threads, coroutines or continuations?
Some OSs do provide the required functionality (e.g, the fibers API
On Tue, May 21, 2013 at 01:46:13PM +0200, Jorge Acereda Maciá wrote:
Hi,
On May 21, 2013, at 7:46 AM, Alexander Burger a...@software-lab.de wrote:
The big question is: Will the system (which system?) do that? If so, how
do other languages implement green threads, coroutines or
Hi Jon,
files on the index list, since they have got URLs like
http://localhost:8080/doc/ref.html;. However, when I run my web.l
on Cloud9 and go to http://demo-project.jkleiser.c9.io/doc/;, then
the URL for doc/ref.html is now
http://demo-project.jkleiser.c9.io/doc/doc/ref.html;; there's
Hi Alex,
On Tue, May 21, 2013 at 7:46 AM, Alexander Burger a...@software-lab.dewrote:
To make things more clear, let's consider the following situation. It is
after the program started two coroutines, and then execution continued
in the main program. The two coroutines are suspended, and the
Hi Rand,
Is that picture a single, contiguous memory region? Because then,
Yes
you *could* have the first scenario I mentioned in a previous mail
(unlikely, but, think of a native C code, that allocated huge
structures and recursed -- it could overwrite many megabytes of
Yes, I'm aware of
Hi Alex,
Yes, by all means, keep the coroutines!
Perhaps add some of this mailing list chain as a caveat about the stack in
the
coroutines documentation: http://picolisp.com/5000/!wiki?coroutines
In particular, the picture of the stack and the warning to allocate enough
stack if
there is any
