I feel like a broken record here, but I'm hoping that if I say it
enough it'll stick in someone's head...
Richard Hartman <[EMAIL PROTECTED]> writes:
> If they want a system function to crash & burn if anything
> goes wrong instead of sending a code back to the caller to
> handle as the caller deems appropriate, at the very least they
> should be documented that way:
>
> this function dies a horrible flaming death if
> anything goes wrong.
Amen, brother.
PalmOS folks: please, please, please, make the Err*() routines save a
stack trace somewhere on the device (perhaps a static area that the
startup code could save to a db... shades of crash dumping onto the
swap partition). This would alleviate the most annoying thing about
the OS-enforced crash-and-burn: the total lack of feedback to the
developer about where the problem lies. "Oh, it crashed in DmWrite()?
That narrows it down a lot."
- Nathan
PS. Before anyone says "POSE", let me pre-counter with (1) beta
testers and (2) non-emulated hardware. I suspect that (2) will become
ever more popular if the Handspring stuff takes off...
