Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!sri-spam!ames!ucbcad!ucbvax!decvax!tektronix!sequent!mntgfx!gssc!jdm
From: jdm@gssc.UUCP
Newsgroups: comp.windows.x
Subject: Re: X on Xenix/386
Message-ID: <269@gssc.UUCP>
Date: Wed, 18-Feb-87 11:15:02 EST
Article-I.D.: gssc.269
Posted: Wed Feb 18 11:15:02 1987
Date-Received: Fri, 20-Feb-87 06:49:03 EST
References: <8702152056.AA17802@tcgould.tn.cornell.edu> <267@gssc.UUCP> <526@spdcc.COM>
Reply-To: jdm@gssc.UUCP (John D. Miller)
Organization: Graphic Software Systems, Beaverton Or
Lines: 24
Summary: premature

i appologize for the wording in my previous posting regarding GSS's X 
implementation.  i should have said, "we are porting," rather than, 
"we have ported."  

we *did* have a running demonstration running at uniform using microsoft system 
v xenix/386, but this is not a released product.  i cannot divulge any info on
the status of this product or any of the technical details.  your best bet is
the trade rags since uniforum.

IMPORTANT: my posting was *not* intended to make any pre-mature announcements, 
but rather to address the question of, "is it okay to write my X application to
never run on anything but BSD?"

the obvious answer is, "no."  even though certain aspects of most any 
application - especially X applications - must utilize certain OS dependent
functions, such as sockets, it is wise to isolate these as much as possible for
ifdefing in a similar function on another OS.  

'nuff said.

-- 
-- jdm
in real life:  John D. Miller, Graphic Software Systems, Inc., Beaverton OR
...!{tektronix!verdix}!sequent!gssc!jdm