🚀 go-pugleaf

In article <B2TABT5R@minnie.zdv.uni-mainz.de> martin@automatix.kph.Uni-Mainz.DE writes:
>Many programs are written with the assumption that sizeof(int) is identical 
>to sizeof any pointer.

Fortunately, not as much anymore, since this is not true on PCs except
in the small model and prototypes are used more often now.

> The system-compiler cc on OSF1/Alpha assumes this also
>with a size of 64bit. This is not so for the gcc produced on this plattform.
>Here has a pointer 64, long 64, int 32 and short 16 bits. So the way 
>for porting software is to change at every place where it is needed
>int to long or to have a compiler option (like -mint64 on SPARC) to say
>gcc to use int with 64 bits (or to use cc).

>What is to do?

It may be useful to have a switch to make int be 64 bits, but it is better
still to fix programs that make this assumption (the alternative is to
waste a lot of memory in some cases.

"lint" is your friend.


--
Joe Buck	jbuck@ohm.berkeley.edu