Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!mit-eddie!genrad!decvax!tektronix!sequent!mntgfx!gssc!jdm
From: jdm@gssc.UUCP
Newsgroups: comp.windows.x
Subject: Re: 'zap'; comp.window.x; BSD unix; keystrokes; event interrupts
Message-ID: <267@gssc.UUCP>
Date: Mon, 16-Feb-87 13:28:33 EST
Article-I.D.: gssc.267
Posted: Mon Feb 16 13:28:33 1987
Date-Received: Tue, 17-Feb-87 22:39:32 EST
References: <8702152056.AA17802@tcgould.tn.cornell.edu>
Reply-To: jdm@gssc.UUCP (John D. Miller)
Organization: Graphic Software Systems, Beaverton Or
Lines: 18

In article <8702152056.AA17802@tcgould.tn.cornell.edu> garry@TCGOULD.TN.CORNELL.EDU (Garry Wiegand) writes:
>3) I need my software to be portable to various X's, but I find myself
>   having to do things in the X driver which are BSD-specific. I don't
>   know: is this unsafe or does X perhaps *only* exist on BSD machines?

NOOOOOOOOOO!!!!!!!  DO NOT COUNT ON X ONLY RUNNING ON 4.X MACHINES!!!!!

We have ported X to System V Xenix/386, and intend on doing more of the
similar.  If you want your application to run in all environments, follows
standard "portable code" procedures and use generic calls, or use ifdefs, etc.

Don't box yourself in!!

-- 

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