On 8/13/07, Toby Murray <toby.murray at comlab.ox.ac.uk> wrote:
> Just to clarify, the purpose of this pattern is to allow one to be able
> to delegate references to (possibly) untrustworthy code, such that the
> code is prevented from hanging on to these references for any longer
> than is necessary for it to perform its function.
>> If so, I think it would be worth stating something to this effect in the
> comments of the code. Not just stating /what/ it does, but /why/, would
> be pretty useful. It wasn't apparent to me what the end result that the
> code was achieving, given the description in the comments, until I read
> the code and the updoc example.
Good suggestion. It's now added.
> Nice stuff. Looks like a pretty useful pattern to me to solve a problem
> that I'm sure many of us have run thought experiments about before.
Agreed, and thanks. The idea is all Jed's.
--
Text by me above is hereby placed in the public domain
Cheers,
--MarkM