Re: [q-lang-users] Bug?

[John C. <co...@cc...>]

Albert Graef scripsit:

> Instead I could also try to work on the stack overflow detection
> heuristic in eval() (line 3515 in qm.c), but AFAIK there is *no*
> portable way to reliably detect an imminent C stack overflow beforehand.
> Or can anyone here prove me wrong and show me such a trick?

Chicken does it somehow; I've sent Felix an email asking him to
explain it.  This is essential, because in Chicken, compiled
procedures just call one another without ever returning, gobbling
up the stack until it's full.  Then a garbage collector evicts
any Scheme objects to the heap and longjmp()s back to start over,
since all the C call frames are garbage.

-- 
John Cowan  <co...@cc...>  http://ccil.org/~cowan
Micropayment advocates mistakenly believe that efficient allocation of
resources is the purpose of markets.  Efficiency is a byproduct of market
systems, not their goal.  The reasons markets work are not because users
have embraced efficiency but because markets are the best place to allow
users to maximize their preferences, and very often their preferences are
not for conservation of cheap resources.  --Clay Shirkey