X Protocol: Match Error does not identify what failed.

[Ralph Corderoy]

Hi,

Some errors, e.g. Window, contain the bad resource ID but the common
Match error doesn't use any of the many spare bytes it has to give the
caller a clue what was disliked in the specified request.  I realise it
would vary per request, but some indication, e.g. the third in a
LISTofVALUE, or a mask, would be helpful.

Is there a historical reason it wasn't done like this?

-- 
Cheers, Ralph.
https://plus.google.com/115649437518703495227/about