Path: utzoo!attcan!uunet!samsung!know!zaphod.mps.ohio-state.edu!swrinde!ucsd!ucbvax!hplabs!hpda!hpwala!hpwade!johns
From: johns@hpwade.hp.com (John Silva)
Newsgroups: comp.windows.x
Subject: Re: what's most important to you for R5?
Message-ID: <980@hpwala.wal.hp.com>
Date: 26 Jun 90 14:52:46 GMT
References: <9006222202.AA17654@expire.lcs.mit.edu>
Sender: netnews@hpwala.wal.hp.com
Reply-To: johns@hpwarf.hp.com (John Silva)
Organization: Hewlett Packard, Waltham, Mass
Lines: 29


  In trying to use Xlib with C++ there are cases where there
are inconsistent definitions of the parameters to the Xlib function
calls.  This causes grief in C++ (or with ANSI C) parameter type
checking !!   Here are a couple of examples :

in

XChangeActivePointerGrab and XGrabPointer() event_mask is defined
as unsigned int,

whereas in

XChangeGC() and XMaskEvent() event_mask is defined as unsigned long !!

also in the Xlib XWindowAttributes structure the all_event_masks,
your_event_mask, and the do_not_propagate_mask are defined as long,
again inconsistent with the four function calls above.

This parameter represents the same type of data ... why is it typed
inconsistently ??  (I imagine that on most 68K machines unsigned long
and unsigned int are the same, but this may not be so on Intel machines.)

There needs to be a cleanup of the parameters (and data structures) in
Xlib to make sure they are consistent and work correctly with ANSI-C and
C++.

Thanks,
  John