> I don't *really* like guard() anyway because it's kind of magic in > that the unlock doesn't actually appear in the code, and it's kind of > hard to unravel what guard() is and how it works. But I guess that's > mostly because it's just a new idiom that takes time to internalize. How will the circumstances evolve further for growing applications of scope-based resource management? Regards, Markus
