Xref: utzoo comp.lang.c++:6452 comp.windows.x:18375 gnu.g++:651
Path: utzoo!attcan!uunet!bu.edu!bu-cs!snorkelwacker!usc!jarthur!uci-ics!rfg
From: rfg@ics.uci.edu (Ronald Guilmette)
Newsgroups: comp.lang.c++,comp.windows.x,gnu.g++
Subject: Re: X11 and C++
Message-ID: <25D887FF.273@paris.ics.uci.edu>
Date: 13 Feb 90 22:19:43 GMT
References: <943@imec.UUCP>
Reply-To: rfg@ics.uci.edu (Ronald Guilmette)
Organization: UC Irvine Department of ICS
Lines: 18

In article <943@imec.UUCP> depuydt@imec.be (Francis Depuydt) writes:
>I would like to use the X11 library functions in my C++ environment.
>However, some keywords of C++ seem to be used for X11 variables. 
>Are there other incompatibilities? Did some of you experience the same
>sort of problem, and what is the 'cheapest' solution?

I have been encouraging the folks at MIT Project Athena and at
the X Consortium to use my protoize and unprotoize tools to whip X11
into condition so that individual end-users could easily generate their
own fully-prototyped versions of X11 (and especially its include files).

There seems to some interest in doing this at both places, but that interest
is tempered by resource (i.e. manpower) limitations.

Regardless of that, I hope that we will all someday enjoy an "easily
protoizable" version of X11.

// rfg