Adam Wozniak <[EMAIL PROTECTED]> wrote:
> Err MemSetV30(void *dstP, Int32 numBytes, UInt8 value)
> SYS_TRAP(sysTrapMemFlood);
>
> Err MemFlood(void *dstP, Int32 numBytes, UInt8 value)
> SYS_TRAP(sysTrapMemFlood);
Thank you. We're familiar with this technique. It sucks.
> Now old code will continue to work, just not compile. You'll have to
> switch to MemFlood() if you want to recompile.
Cue Andreas Linke... :-)
I'm surprised to hear one of our developers advocate this technique.
I'm curious: why do you think it's a good technique? Presumably you have
a large collection of existing source code. Why is it in your interest
to have to change MemSet() calls in working code all over the place
just to compile with a new SDK? Surely you would save time and money
if the new SDK, while offering the improved MemFlood() for new code,
continued to compile your existing code correctly?
John
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
