Re: [Caml-list] Scoped Bound Resource Management just for C++?

[Florian Weimer <fw@deneb.enyo.de>]

> Scope-bound resource management is inherently broken, at least
> without sophisticated type system support.

If the environment supports communicating processes with separate
execution pointers, it is straightforward to bypass restrictions, no
matter how evolved the type system is.

> 2) or it is unsafe, i.e. you can access an object after its life time has
> ended, with potentially desastrous effects.

This can be made safe with type-safe memory and run-time checks.  I
don't think this is a good excuse.

In the end, this is about making it as easy as possible for
programmers to write resource-aware programs.  After all, the
challenge is that code without proper resource management seems to be
correct for small sample inputs, so problems are likely noticed only
much, much later.