Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!snorkelwacker!apple!voder!parns!michael
From: michael@parns.nsc.com (Michael C. Wagnitz)
Newsgroups: comp.windows.x
Subject: Re: xterm problems (SUN server)
Keywords: R4 bug compatibility
Message-ID: <168@harley.nsc.com>
Date: 20 Nov 89 17:39:28 GMT
References: <215@isgtec.UUCP> <8911181646.AA23541@expire.lcs.mit.edu>
Reply-To: michael@parns.nsc.com (Michael C. Wagnitz)
Organization: National Semiconductor Corporation, Santa Clara
Lines: 18

In article <8911181646.AA23541@expire.lcs.mit.edu> rws@EXPO.LCS.MIT.EDU (Bob Scheifler) writes:

> The R3 xterm is buggy, as are numerous other R3 clients that use an illegal
> do-not-propagate-mask value.
>                      The MIT R4 server will similarly be offended, although
> the R4 server provides a "bug compatibility" mode to allow broken clients
> to continue to operate.

Do you suppose it would be possible for someone 'in the know' to publish here
a list of known coding fax paus typically created as a result of using the
existing R[23] client sources as reference on 'how to do' X11 applications?

Such a list would aid many of us in repairing our applications for use under
an R4 ICCM-compliant window manager, et.al.  Especially useful would be any
examples of 'illegal' coding practices seen by the consortium to cause
potential failure when using a fully compliant window manager.

Thanks in advance for any considerations.