Summary: | XCBProtocolRequest structure ought to have flags bitmask | ||
---|---|---|---|
Product: | XCB | Reporter: | Jamey Sharp <jamey> |
Component: | Library | Assignee: | Jamey Sharp <jamey> |
Status: | RESOLVED WONTFIX | QA Contact: | xcb mailing list dummy <xcb> |
Severity: | enhancement | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Jamey Sharp
2006-05-02 06:26:03 UTC
Replacing xcb_protocol_request_t.isvoid with a uint8_t "flags" bitmask would be ABI-compatible, as long as isvoid is the least-significant bit, but it would need a bit of care to stay API-compatible. This may still be worth doing. I don't think there's any point until we actually want a second flag, at which point yes, it's fine. If we haven't needed one until now, we presumably never will. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.