More NULL questions

[Bob Devine]

In article <903 at abvax.UUCP>, aep at ivan (Alex E. Pensky) writes:
> Even if pointers and integers are the same size and have the same 
> representation, you are still in trouble if your compiler passes int
> parameters and pointer parameters via different mechanisms.  In such
> a case, omitting both the prototype and the cast will mean that the *entire*
> parameter list will be received incorrectly by my_func().
> Yes, such compilers exist, and yes, I have been bitten by one after
> forgetting the casts.

  What different mechanisms?  C only supports call-by-value for
parameters (I'm ignoring the special casing of arrays here).  How
can pointers be passed differently than ints?  It sounds like you
used a broken compiler.