[Kazimir talks about garbage collection limits.] > I tried it only on Icon 9.3.2. for Windows. Does it work better on some > other version of Icon or Unicon?
Here is a summary of where we are at: The Icon and Unicon sources use recursive garbage collection functions which use C stack space proportional to the maximum "depth" of the Unicon/Icon structures being visited. I think Windows Icon 9.3.2 has a substantially smaller C stack than Windows Unicon; the numbers might be 40K versus 768K, so you might see a 10X to 20X increase before stack failure on Windows Unicon. Switching to Linux or another UNIX (or Cygwin) might gain you another 10X or might remove the stack limit entirely (the stack seems to be 8M for some Linux processes, and unlimited for others). As soon as we can get around to it, we will (a) raise the stack limit on Windows Unicon by another order of magnitude or so, and (b) add code for dynamically increasing the stack limits on those platforms which support this (e.g. Linux). In future, someone might like to look at rewriting the garbage collector markptr() and markblock() functions to remove the recursion, or figure out how to raise the C stack limits dynamically on Win32. Clint ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ Unicon-group mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unicon-group
