Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!seismo!brl-tgr!tgr!geacc022%timevx@CIT-HAMLET.ARPA
From: geacc022%timevx@CIT-HAMLET.ARPA
Newsgroups: net.lang.c
Subject: Portablility problems
Message-ID: <12@brl-tgr.ARPA>
Date: Fri, 19-Jul-85 05:57:12 EDT
Article-I.D.: brl-tgr.12
Posted: Fri Jul 19 05:57:12 1985
Date-Received: Sat, 20-Jul-85 12:34:16 EDT
Sender: news@brl-tgr.ARPA
Lines: 19


    I am going to be attempting to write 'portable' C code, and I
would like to know what some of the traps are that people who grew
up in Ye Olde Classic Vax Environment should look out for.  I already
know about the sizeof int == 2 or 4 bytes; and the int != char * != xxx *
problems.  Another one that came to mind when I was reading some of
my old code was that our compiler allows you to take that address of
a function parameter -- but machines that pass parameters in registers
probably won't let me do that.

    I don't need to know about Reiserisms, since our compiler never
supported those anyway; but what other problems have people had
trying to port code from a Vax?  Respond to me, and I'll summarize
for the net.  Thanks in advance,

			Gary Ansok
			GEACC022%TIMEVX @ CIT-HAMLET.ARPA
			GEA @ CALTECH.BITNET
			...ucbvax!cithep!timevx#geacc022