Simon,
Thank you for explanation.
- We have an accurate GC, which means that the Haskell stack can be
movable, whereas the C stack isn't. So we can start with small
stacks and enlarge them as necessary.
What is the difference between the Haskell stack and the C stack?
I guess that
On 07/09/2011 08:13, Kazu Yamamoto (山本和彦) wrote:
Simon,
Thank you for explanation.
- We have an accurate GC, which means that the Haskell stack can be
movable, whereas the C stack isn't. So we can start with small
stacks and enlarge them as necessary.
What is the difference
Hello Simon,
Now everything is clear to me. I wrote a blog article on this in
Japanese.
Thanks.
--Kazu
On 07/09/2011 08:13, Kazu Yamamoto (山本和彦) wrote:
Simon,
Thank you for explanation.
- We have an accurate GC, which means that the Haskell stack can be
movable, whereas the C
Hello,
Recently I exchanged information about user threads with Ruby
community in Japan.
The user threads of Ruby 1.8 are heavy weight and Ruby 1.9 switched to
kernel threads. The reason why user threads of Ruby 1.8 are heavy
weight is *portability*. Since Ruby community does not want to prepare
On 06/09/2011 09:47, Kazu Yamamoto (山本和彦) wrote:
Recently I exchanged information about user threads with Ruby
community in Japan.
The user threads of Ruby 1.8 are heavy weight and Ruby 1.9 switched to
kernel threads. The reason why user threads of Ruby 1.8 are heavy
weight is *portability*.