🚀 go-pugleaf

>] In fact, the situation with Alpha is very similar to the current situation
>] with Macintosh and 16-bit Windows programs, with the sizes doubled of course.
>] You will run into the same types of problems around 2 GB on the Alpha as we
>] currently run into at 32 KB with Mac and Windows programs.  Of course these

32KB? I see, 16 bit (int). However, 68K pointers have always been 32 bits.
Nowadays, (int) usually is too. Still, embedded 68K systems sometimes try to
get by with halfwords. And really small ones store halfword pointers, knowing
that they don't have more than, e.g., 24K of memory.

>For example, when you call "fscanf(fp, "%d", &value);", we need to be clear on
>what size `value' is meant to be, or you get nasty memory corruption problems.

Typically, compiler and runtime library have to agree on (sizeof(int)), etc.
Often you're given a choice of library. And that's why we have "%ld" and (long).
--
	Alex Colvin
	alex.colvin@dartmouth.edu
	alex_colvin@fostex.com