🚀 go-pugleaf

> You also have to be careful when passing arguments because the C compiler
> does not automatically convert everything to long words when passing arguments
> on the stack. chars and ints use MOV.W data,(SP)- and pointers and longs
> use MOV.L data,(SP)-. This can can a crash due to bus errors because if
> you're not careful you could pick up an invalid pointer.
> 
> Don't ask me why they decided to do it this way, probably just to cut down
> on generated code and improve speed, but it definately will cause problems
> with LOTS of software that assumes that arguments passed to function are
> the same size and resized to the proper size by the called function.

There is certainly precedent for this sort of thing: the original Ritchie
compiler did things this way. If your code assumes that int promotes to long
or to (void*) on a function call it will die on more machines than just this
one.

Now why they didn't follow the VAX' precedent and make ints 32 bits, and shorts
16 bits, I don't know. Are you sure that the compiler uses 16-bit ints? Strikes
me as silly on a 68000.