Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!umich!samsung!uunet!sco!mikep
From: mikep@sco.COM (Mike Patnode)
Newsgroups: comp.windows.x
Subject: Re: #ifdef in Xlibos.h
Message-ID: <5647@scolex.sco.COM>
Date: 12 Apr 90 17:58:10 GMT
References: <5594@scolex.sco.COM> <9004111514.AA11945@kanga.lcs.mit.edu>
Sender: news@sco.COM
Reply-To: mikep@sco.COM (Mike Patnode)
Organization: The Santa Cruz Operation, Inc.
Lines: 41


In article <9004111514.AA11945@kanga.lcs.mit.edu> jim@EXPO.LCS.MIT.EDU (Jim Fulton) writes:
+>
+>	Shouldn't line number 7 in X11/Xlibos.h be
+>
+>	#ifdef SYSV
+>
+>	instead of
+>
+>	#ifdef att

+>The block in question probably has more to do with STREAMSCONN than USG (SYSV

Agreed.  Some SVR3 derivatives may not want to use streams.

+>Possibly, but not necessarily.  There are 4 symbols used in R4 for System
+>V-ish things:
+>
+>	SYSV			SVR2 systems
+>
+>	USG			SVR3 systems
+>
+>	att			AT&T 6386 running V.3.2 ("pure UNIX"?)

The #ifdef att stuff sort of sneaks up on you.  (It's also prevelent in
xterm)  The SYSV and USG stuff is well document elsewhere (Release Notes
, imakemdep.h, etc).

It seems to me that all the #ifdef att's should be #ifdef USG's since I
can't imagine the case where you would see:

#if defined(att) && !defined(USG)

Any decenting opinions?


-- 
Mike Patnode					The Santa Cruz Operation 
SCO Software Engineer				400 Encinal Street
{ucscc,uunet}!sco!mikep	 mikep@sco.COM  	P.O. Box 1900
(408) 458-1422                                  Santa Cruz, CA 95061