At 01:22 AM 9/23/99 -0700, you wrote: >And how many of those functions should have such warnings? Probably a lot! If >you were to call memset(NULL, 0, 256), what should be the correct behavior? For >a dialog to appear saying that NULL was passed when it shouldn't have been, or a >Sad Mac or UAE dialog to appear? I can't see why anyone wouldn't prefer the >former. The thing you don't get is that the former is only happening because you fail to handle the exception that is thrown during the call to memset(). The proper behaviour is to throw an exception, not put up some goofy message the developer can't do a damn thing about. "StringMgr.c:4375, NULL string passed" indeed - how does that help anyone?
- PalmOS improvements (was: C++ SDK wanted!) Andreas Linke
- Re: PalmOS improvements (was: C++ SDK wanted!) krollin
- Re: PalmOS improvements (was: C++ SDK wanted!) Michael Yam
- Re: PalmOS improvements (was: C++ SDK wanted!) Jason Dawes
- Re: PalmOS improvements (was: C++ SDK wanted!) David Fedor
- Re: PalmOS improvements (was: C++ SDK wanted!) Jason Dawes
- Re: PalmOS improvements (was: C++ SDK wanted!) David Fedor
- Re: PalmOS improvements (was: C++ SDK wanted!) Jason Dawes
- Re: PalmOS improvements (was: C++ SDK wanted!) B. Flaumenhaft
- Re: PalmOS improvements (was: C++ SDK wanted!) Chris Antos
- RE: PalmOS improvements (was: C++ SDK wanted!) Richard Hartman
- Re: PalmOS improvements (was: C++ SDK wanted!) Jason Dawes
- Re: PalmOS improvements (was: C++ SDK wanted!) Roger Chaplin
- Re: PalmOS improvements (was: C++ SDK wanted!) Bill Goodman
