Alex,
That looks great! I'm very impressed with native and now he doc!
Cheers!
Rand
On May 9, 2012, at 3:33 PM, Alexander Burger wrote:
> Hi all,
>
> at last, I have found the time to write an in-detail description of the
> 'native' function:
>
> http://software-lab.de/doc/native.html
>
>
I won't try to "point" to documentation
Each co-routine should have it's own separate stack. Best practices with
stack management today have a sufficiently large stack that grows and then
terminates in unmapped memory. If it is attempted to grow the stack too
much, then the program gets a memor
Hi Alex,
On Tue, May 21, 2013 at 7:46 AM, Alexander Burger wrote:
>
>
> 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 hardware
> stac
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 chan
Good bye Rand Dow :-(
You are now unsubscribed
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
