Portablility problems
geacc022%timevx at CIT-HAMLET.ARPA
geacc022%timevx at CIT-HAMLET.ARPA
Fri Jul 19 19:57:12 AEST 1985
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
More information about the Comp.lang.c
mailing list