RNG <[EMAIL PROTECTED]> writes:
> in memory, but what about calls like: 
> 
>       strcpy (pos, string);
> or
>       memcpy (new_mem, mem, byte_size);
> 

This is quite different from what we were talking about. In the
wrong-callback case you are basically lying to the compiler about the
function type; for example you take a function that does return a
value, and you cast it to a function that does not, and then you call
it.

In the above case, the compiler knows full well the type of the
function and can be expected to compile it properly.

Havoc

-- 
To unsubscribe: mail -s unsubscribe [EMAIL PROTECTED] < /dev/null

Reply via email to