On Aug 6, 2006, at 12:28 AM, CV wrote:
On Aug 5, 2006, at 8:46 PM, John Balestrieri wrote:
I thought the stack space was increased a couple of years ago? If
that was the case, it looks like it's be knocked down again.
I don't think that it has been increased. I may have missed
something, although any mention of 32k stack limitation catches my
eye since I was bitten by it in 5.0.
A useful technique for dealing with stack space limitations is to run
your recursive routine in a thread, catch the stack overflow
exception, and spawn a further thread to carry on.
Even easier is just to do each recursive step in its own thread. The
thread halts, but the next thread can keep a reference to the
previous one, so it will still hang around to gather information from
when you're done. Often you don't even need to do that.
Of course, this will be *significantly* slower.
Guyren G Howe
guyren-at-relevantlogic.com
http://relevantlogic.com
REALbasic, PHP, Python programming
PostgreSQL, MySQL database design and consulting
Technical writing and training
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
