THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 28/03/2012 at 06:54, xxxxxxxx wrote:
I think I recently saw a post about the max limit and/or flipping
the max count returned by GetDirty().
Does it reset at some point (like at 10000k or something) or
is it advisable to to a modulo of it to be "safe"
On 28/03/2012 at 07:31, xxxxxxxx wrote:
Found the post I thought was but it was about GeGetTimer(),
so the q remains , does the GetDirty() return wrap at some point?
On 29/03/2012 at 08:13, xxxxxxxx wrote:
Unless anyone see any issue with GetDirty() count return, I imagine
it can't be that critical as I guess it's done all the time for any generators (primitives)?
I use the GetDirty() for my own generators and store the sum off the return
for all objects used by the generators in their own basecontainers and
bypass the Cache if stored and checked sum differs.
On 29/03/2012 at 09:56, xxxxxxxx wrote:
Depending on what type the internal flag is of, the value needs to reset at a specific point. If it is
stored as a 32-bit integer value, the maximum value it can hold is 2 ** 32 - 1. But trust me, you'll
never reach that many dirtycounts.
On 29/03/2012 at 12:22, xxxxxxxx wrote:
I guess that would be plenty enough
On 30/03/2012 at 01:16, xxxxxxxx wrote:
GetDirty() returns a ULONG and it can have any value within this range.
Few functions use a LONG instead but this is just a cast from ULONG.
And the wrapping shouldn't be a problem, as in most cases we just want to test if the dirty checksum is different than the previous one.
On 30/03/2012 at 05:19, xxxxxxxx wrote:
Ah, thanks! Does this means that I should Set/GetLong() for my base container storage?
Right now I use Set/GetReal() or is that irrelevant?
On 30/03/2012 at 06:25, xxxxxxxx wrote:
You should always use the appropriate method to get and set values in a container.
On 30/03/2012 at 08:18, xxxxxxxx wrote:
I'm glad I asked, now I saw there's a Get/SetLLong() as well:)