include: document _XkbErrCode2 macros
Why sending the number of the (implementation-dependent) error statement to the client is a good idea is a bit beyond me, but at least document it so we can all share the despair. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Daniel Stone <daniel@fooishbar.org>
This commit is contained in:
parent
7100118c8d
commit
191b630656
|
@ -301,6 +301,11 @@ extern _X_EXPORT const char *XkbBinDirectory;
|
|||
extern _X_EXPORT CARD32 xkbDebugFlags;
|
||||
|
||||
#define _XkbLibError(c,l,d) /* Epoch fail */
|
||||
|
||||
/* "a" is a "unique" numeric identifier that just defines which error
|
||||
* code statement it is. _XkbErrCode2(4, foo) means "this is the 4th error
|
||||
* statement in this function". lovely.
|
||||
*/
|
||||
#define _XkbErrCode2(a,b) ((XID)((((unsigned int)(a))<<24)|((b)&0xffffff)))
|
||||
#define _XkbErrCode3(a,b,c) _XkbErrCode2(a,(((unsigned int)(b))<<16)|(c))
|
||||
#define _XkbErrCode4(a,b,c,d) _XkbErrCode3(a,b,((((unsigned int)(c))<<8)|(d)))
|
||||
|
|
Loading…
Reference in New Issue
Block a user