Mail Archives: djgpp/1996/04/09/04:29:24
On Mon, 8 Apr 1996, Jethro Wright wrote:
> >But beware: when a C compiler sees this, it actually generates code to
> >call `newfn' with a calling sequence that is appropriate for `oldfn'. In
> >this case, it converts `s' from int to unsigned int, but other subtle
> >things might be going on there too. This is what casting function
> >pointers means. It's best to avoid it, unless you can't do otherwise.
>
> Eli, it has always been my understanding that casts in
> C *don't* do conversions (at least, for casts bet integral types),
This is NOT true for casting functions. When you call a casted function,
the stack and the variables it gets are set up according to the cast.
Otherwise, casting function would have no effect at all, except escaping
the compiler type-checks (which is not what it is meant to do).
- Raw text -