On Mon 20 Aug 2012 05:22, Alex Shinn <alexshinn@gmail.com> writes:

> It's expected that implementations close files on
> gc, and a good implementation should gc when out
> of file descriptors as well.  An alternate approach
> to more timely releasing of resources would be
> to add stronger guarantees about when gc occurs -
> again, an area of open research not yet ready for
> WG1.

Leaving file closing to GC is the wrong thing to design for.  It's an OK
fallback but it's not a good base case.

Part of the reason is that files are closed during finalization, which
does not have to run when GC runs.  The Java world, for example, has
standardized on running finalizers in a separate thread.  Guile does
this as well, when possible.  So running GC might not have the effect of
closing files.

There are a number of Scheme systems out there that support what Peter
and I want to do.  Guile's `with-throw-handler' is one example.  I'm
sure Chicken has something as well.

Regards,

Andy
--
http://wingolog.org/

_______________________________________________
Scheme-reports mailing list
Scheme-reports@scheme-reports.org
http://lists.scheme-reports.org/cgi-bin/mailman/listinfo/scheme-reports