Path: utzoo!mnetor!uunet!husc6!uwvax!oddjob!gargoyle!ihnp4!inuxc!iuvax!silver!backstro
From: backstro@silver.bacs.indiana.edu (Dave White)
Newsgroups: comp.lang.c
Subject: Re: Are the criteria for Unix and PC compilers different?
Message-ID: <1124@silver.bacs.indiana.edu>
Date: 7 Mar 88 16:31:09 GMT
References: <22314ad9@ralf.home>
Reply-To: backstro@silver.UUCP (Dave White)
Organization: Indiana University BACS, Bloomington
Lines: 21
Summary: #define int long won't fix precompiled libraries!

In article <22314ad9@ralf.home> Ralf.Brown@B.GP.CS.CMU.EDU writes:
>In article <1106@silver.bacs.indiana.edu>, backstro@silver.bacs.indiana.edu
>(Dave White) writes:
>}When will [PC C compiler vendors] realize that some of us really want
>}the option of using 32-bit ints to port Unix-born code?  
>
>#define int long
>
>Need I say more?
It isn't that simple. Your suggestion would ensure that the
compiler thought the code I was compiling saw ints and longs
the same way, but this would not be the case with the compiler's
run-time library, which would need to be recompiled and debugged.
alloc and friends, for example, take int-sized arguments in my machine!

I want to port code, not support a compiler (the code is enough trouble
as it is :-)
If we want to coverse further, perhaps we should do so by mail -- let;s
not clutter up the newsgroup!
--
backstro@silver.bacs.indiana.edu