In message <[EMAIL PROTECTED]>
Dave Storrs <[EMAIL PROTECTED]> wrote:
> This runs into problems if you currently have an iterator extant and you
> modify the hash to which it points. Immediate suggestions on how to
> handle this would be:
>
> 1) Do what the docs currently do; tell people "don't do that"
> 2) Have the iterator auto-reset when the hash is modified
> (probably bad)
> 3) Make the hash unmodifiable while there is an iterator extant
> (probably bad)
> 4) Make powerful magic in some way that isn't coming to mind
See the "Freezing state for keys and values efficiently" section
of RFC 136 for some powerful magic that could achieve this...
Tom
--
Tom Hughes ([EMAIL PROTECTED])
http://www.compton.nu/
...Reading is thinking with someone else's head instead of one's own.
