[comp.windows.x] How much of X.h can we assume is unchanging?

pds@quintus (Peter Schachte) (09/14/88)

What parts of the X.h include file can one assume won't change, either
over time, or between vendors?  Is None always going to be 0?  Or is
the whole file just a bunch of convenient defines for constants that
are part of the protocol, and will never change?  This is important for
interfacing to other languages.

Thanks in advance for any help.

-Peter Schachte
pds@quintus.uucp
..!sun!quintus!pds

jim@EXPO.LCS.MIT.EDU (Jim Fulton) (09/20/88)

> What parts of the X.h include file can one assume won't change, either
> over time, or between vendors?

Things that are documented in the Xlib manual will remain constant.


Jim Fulton
MIT X Consortium

RWS@ZERMATT.LCS.MIT.EDU (Robert Scheifler) (09/27/88)

    Date: 13 Sep 88 20:06:46 GMT
    From: quintus!pds@unix.sri.com  (Peter Schachte)

    What parts of the X.h include file can one assume won't change, either
    over time, or between vendors?

Basically all of it.  (Well, X_PROTOCOL_REVISION might increment ...)

    Is None always going to be 0?

Yes.

    Or is
    the whole file just a bunch of convenient defines for constants that
    are part of the protocol, and will never change?

True of the numeric constants.  The typedefs are specific to C,
but there should be no reason to change them either.