On Tue, Jan 24, 2012 at 01:34:08PM -0500, Gaetan Nadon wrote: > Oh, wait a minute. There is a reason why it is not there to begin with. > Isn't it a "private" header? Making it public will make it impossible to > make backward compatible changes. Code written for xaw3d may want to be > ported on xaw and will put pressure on libxaw to make it public as well. > > If gv wants to break the rule and use private header, they have to do > the workarounds. That is what usually the capital P stands for, but I > could be wrong.
Often "P" means private. This header file (XawImP.h) declares the resource names used for input-methods that would use Xaw(3d). Generally resource names are in a "public" header; without those the library is less useful. This header declares private functions as well, and there is no "public" version of the header file, probably because only the resource names would comprise its contents. X headers are not always consistent - keyboard stuff is an example... Take a look at the Shell[IP].h variations as well. All of the other resource names defined by Xaw are in "public" headers. Likewise, fixing the problem by moving the #define's (into a newly created "public" XawIm.h) won't help existing applications that use the headers. Compatibility is always an issue. -- Thomas E. Dickey <dic...@invisible-island.net> http://invisible-island.net ftp://invisible-island.net
signature.asc
Description: Digital signature
_______________________________________________ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel