Remi Turk <[EMAIL PROTECTED]> writes: > IMO, [bracket] does indeed have those same drawbacks. (Although the > traditional "explicit memory management model" is alloc/free, > which is much worse than bracket/withFile)
Isn't bracket more like stack allocated memory? And most problems with explicit memory management related to heap (as you indicate)? > The theoretical solution (and probably _only_ theoretical) is > implementing a lot of garbage collectors: one for memory, one for > open files, one for sockets, one for 3D polygon meshes etc etc... ...or have a number of available file handles that is limited by memory? :-) -kzm -- If I haven't seen further, it is by standing in the footprints of giants _______________________________________________ Haskell-Cafe mailing list [EMAIL PROTECTED] http://www.haskell.org/mailman/listinfo/haskell-cafe
