TimeRange.always() is inconsistent
Bug #614295 reported by
Michal Hruby
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Zeitgeist Framework |
Fix Released
|
Medium
|
Seif Lotfy |
Bug Description
There's an inconsistency in TimeRange.always() produced by ZG and libzg. ZG uses (-maxint, maxint), while libzg uses (0, maxint). This introduces incompabilities when using ZG's TimeRange.
Our mightly leader Seif decided that ZG should also use (0, maxint), so this is a reminder to change it for the next release.
Related branches
Changed in zeitgeist: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
2010/8/6 Michal Hruby <email address hidden>:
> Our mightly leader Seif decided that ZG should also use (0, maxint), so
> this is a reminder to change it for the next release.
I disagree, if we are using signed integers then "always" includes the
negatives one. (Another thing is whether it really makes sense to have
signed integers or we should switch to unsigned ones, which I think we
should do).