Re: List container strawman 1.3

[Darren New <dnew@san.rr.com>]

Ted Dennison wrote:
> Suppose a new node got added right after the deletion? In that case its quite
> possible that your iterator is now unintentionally pointing to the new node
> instead of the old deleted one.

True, I'd forgotten about that. There's ways around that too, but
they're higher overhead. Or you could do something with storage pools to
prevent it, perhaps. Doing the invalidation at the time of the operation
is probably a good idea, given that 'iterators' would need to be
controlled (if not limited) anyway, eliminating the need to check on
iterators you don't know about when you make the changes to the list.

-- 
Darren New 
San Diego, CA, USA (PST). Cryptokeys on demand.
   You will soon read a generic fortune cookie.