On Jul 28, 2009, at 11:35 PM, Vincent Manis wrote:
Are these `officially' in Ikarus? (By that I mean is the documentation
status `not yet' rather than `no way am I *ever* going to document
them'
:-)
I do intend to support these. They are in the ``not yet but should be
documented'' category.
On the same topic, is there any plan to have something like Chez's
collect-request-handler, or some similar mechanism? (Or maybe I missed
an existing mechanism when peering through source code?)
There isn't one in Ikarus currently. I need to think about it more
before committing to the idea. (these handlers would run concurrently
with the program, and may fire at any point, and they themselves may
cause further recursive GC/handler calls, which would be fun to debug
to say the least)
I guess it's pretty obvious that I'd like to be able to finalize and
reap inaccessible values registered with a guardian automatically
on GC.
What kind of resource are you protecting? Is the usual strategy (e.g.,
finalizing dead resources when new resources are created) not sufficient
in your case? This is what Ikarus uses for file handlers.
Aziz,,,
