Closed
Bug 962189
Opened 10 years ago
Closed 10 years ago
Endianness of AppFeature Bits
Categories
(Marketplace Graveyard :: Code Quality, defect, P4)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: mstriemer, Unassigned)
Details
New features are added to the AppFeature bit mask as the least-significant bit. This causes the bit numbers to change for each feature when we add new features and the resulting int value to change for the same feature set across versions. Perhaps the new features should be added as the most-significant bit.
Reporter | ||
Comment 1•10 years ago
|
||
Purple is clearly the right colour. I think this should change so that old feature bit masks don't need to change when we start supporting new features. If an app has a feature int value of 34 then supporting new features on Marketplace shouldn't change it, only changing the feature set the app requires should change the int value.
Reporter | ||
Updated•10 years ago
|
Priority: -- → P4
Comment 2•10 years ago
|
||
What does this bug consist of? Just changing the documentation to say "append" instead of "prepend" or is there code to write? Trying to get a feel for how long it would take.
Reporter | ||
Comment 3•10 years ago
|
||
I don't think there should be code to change, we can just start putting new features on the top of the list.
Comment 4•10 years ago
|
||
So...what is this bug then? :)
Comment 5•10 years ago
|
||
Closing as I think this was just documentation confusion. Reopen if I'm wrong.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•