Eliminate boilerplate around client->noClientException.

Just let Dispatch() check for a noClientException, rather than making
every single dispatch procedure take care of it.

Signed-off-by: Jamey Sharp <jamey@minilop.net>
Reviewed-by: Daniel Stone <daniel@fooishbar.org>
This commit is contained in:
Jamey Sharp 2010-05-10 20:22:05 -07:00
commit 92ed75ac59
52 changed files with 475 additions and 621 deletions

View file

@ -1535,7 +1535,7 @@ ProcSetModifierMapping(ClientPtr client)
rep.success = rc;
WriteReplyToClient(client, sizeof(xSetModifierMappingReply), &rep);
return client->noClientException;
return Success;
}
int
@ -1561,7 +1561,7 @@ ProcGetModifierMapping(ClientPtr client)
free(modkeymap);
return client->noClientException;
return Success;
}
int
@ -1619,7 +1619,7 @@ ProcChangeKeyboardMapping(ClientPtr client)
stuff->keyCodes, NULL, client);
}
return client->noClientException;
return Success;
}
int
@ -1722,7 +1722,7 @@ ProcGetKeyboardMapping(ClientPtr client)
free(syms->map);
free(syms);
return client->noClientException;
return Success;
}
int