Bug 734 - The uptodate and changed fields collide somewhat
Summary: The uptodate and changed fields collide somewhat
Status: ASSIGNED
Alias: None
Product: Direct Objects
Classification: Unclassified
Component: Speed (show other bugs)
Version: unspecified
Hardware: PC Linux
: P1 normal
Assignee: Werner Van Belle
URL:
Depends on:
Blocks:
 
Reported: 2011-01-07 15:15 CET by Werner Van Belle
Modified: 2011-01-07 15:16 CET (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Werner Van Belle 2011-01-07 15:15:19 CET 
If we changed something it is clearly uptodate
So we only have three states
a- changed (then it is also uptodate)
b- uptodate (then it has not been changed yet)
c- neither (it is neither uptodate nor changed)

Bitfields might be a very reasonable solution so that a changed flag always set the uptodate flag as well.