Wrong information in WM standard

[Havoc Pennington]

Hi,

On Wed, Oct 29, 2008 at 6:03 AM, Frank Schmitt <ich at frank-schmitt.net> wrote:
> When you look at
> http://standards.freedesktop.org/wm-spec/latest/ar01s05.html#id2569669
> it clearly states, that each pixel is represented by a 32 bit
> integer. In fact the data type is however CARDINAL. CARDINAL is long and
> long is 64 bit under Linux and therefore if you do something like

This 32/64 bit screwup is an Xlib historical mistake (bug) that can't
be fixed since it's now locked into the Xlib ABI, even though it is
one of the most common 64-bit portability problems for X apps.

But CARDINAL is always 32 bits in the protocol and thus in the wm
spec. The bug is in Xlib rather than the specs and protocol.

See:
http://mail.gnome.org/archives/wm-spec-list/2003-March/msg00067.html

Havoc