Re: Caching with custom elements

[Roger H. <rog...@mi...>]

On 15 Feb, 2007, at 21:43, James Walker wrote:

>
>> I see. Would a Q3Shared_DecrementEditIndex be very slightly less
>> dangerous?
>
> Perhaps... but I can imagine having a situation where you're going  
> to be
> doing several operations that you don't want to affect caches, and it
> would be easier to get the edit index, do the operations, and set the
> edit index, rather then figure out exactly how much you need to
> decrement the edit index.
>
> By the way, Q3Shared_Edited isn't actually documented to increment the
> edit index, though that's what it does.  The docs just say "change the
> edit index".

Right.

The other thing I was thinking about was a save and restore mechanism
but I initially thought the decrement was better. The save and  
restore is
essentially the same as your get and set but could have an opaque data
structure.

By the way, has anyone thought much about a 64 bit version of Quesa yet?

Roger.