Xref: utzoo comp.lang.c++:13333 comp.lang.c:39129
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!jarthur!uunet!munnari.oz.au!goanna!ok
From: ok@goanna.cs.rmit.oz.au (Richard A. O'Keefe)
Newsgroups: comp.lang.c++,comp.lang.c
Subject: Re: 64 bit architectures and C/C++
Message-ID: <5662@goanna.cs.rmit.oz.au>
Date: 9 May 91 03:58:00 GMT
References: <168@shasta.Stanford.EDU> <6157@trantor.harris-atd.com> <470@heurikon.heurikon.com>
Followup-To: comp.lang.c
Organization: Comp Sci, RMIT, Melbourne, Australia
Lines: 13

In article <470@heurikon.heurikon.com>, daves@ex.heurikon.com (Dave Scidmore) writes:
> I'm supprised nobody has mentioned that the real solution to this kind
> of portability problem is for the original programmer to use the
> definitions in "types.h" that tell you how big chars, shorts, ints,
> and longs are.

Why be surprised?  I'm using an Encore Multimax running 4.3BSD, and
on this machine there _isn't_ any types.h file.  We have a copy of GCC,
so we _have_ access to the ANSI file, but that's <limits.h>, not "types.h".

-- 
Bad things happen periodically, and they're going to happen to somebody.
Why not you?					-- John Allen Paulos.