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
- [gtk-list] Re: Apprarently simple signal/event question Peter Garner
- [gtk-list] Re: Apprarently simple signal/event quest... Havoc Pennington
- [gtk-list] Re: Apprarently simple signal/event q... Paul Carter
- [gtk-list] Re: Apprarently simple signal/eve... Havoc Pennington
- [gtk-list] Re: Apprarently simple signal... Joe Pfeiffer
- [gtk-list] Re: Apprarently simple signal... Lars Hallberg
- [gtk-list] Re: Apprarently simple signal/event q... RNG
- [gtk-list] Re: Apprarently simple signal/eve... Joe Pfeiffer
- [gtk-list] Re: Apprarently simple signal... M. David Krauss
- [gtk-list] Re: Apprarently simple signal/eve... Havoc Pennington
- [gtk-list] Re: Apprarently simple signal/event quest... Peter Wright
- [gtk-list] Re: Apprarently simple signal/event q... Havoc Pennington
- [gtk-list] Re: Apprarently simple signal/event quest... Peter Garner