I'll grant that it might be nice to have the
option available to let the OS do the reporting
and kill your app ... but bear in mind that this
-could- result in your not being able to take
corrective actions that really might need to be
taken.
Also: it's one thing for a routine that -does-
something (like "save this record") to behave
in that manner ... it's another thing for a
function that is supposed to merely -check-
things to do so (I remember that at least one
checking function will never return a failure
due to this behavior, but I forget which one it
was...)
At best, this behavior should be an option
that you can elect to take advantage of. It
should not be forced upon you.
--
-Richard M. Hartman
[EMAIL PROTECTED]
186,000 mi./sec ... not just a good idea, it's the LAW!
> -----Original Message-----
> From: Chris Antos [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, June 17, 1999 4:57 PM
> To: [EMAIL PROTECTED]
> Subject: Re: DmFindRecordByID
>
>
> i used to agree with that request. but the more i code for
> the PalmOS, the
> more convinced i am that the current paradigm is best. when
> a function
> receives invalid parameters, etc, it should die. this
> actually makes it
> easier to debug the problem, because the error is forcibly
> reported at the
> earliest possible detection of it. it also helps prevent
> data corruption
> that could arise from an app not correctly handling an error
> returned by an
> API. though i'm sure your code is perfect, just like mine
> <tongue in cheek,
> wink>.
>
> however, it would be interesting to see an API that toggles
> Off the fatal
> error messages. this would allow an app to turn them off and
> provide its
> own error handling if it really wants to. the thing is,
> almost every single
> fatal error that can pop up is the result of an actual bug in
> an app's code.
> so if the app has the bug in the first place, why should i
> trust the same
> app to robustly clean itself up??
>
>
>
> ----- Original Message -----
> From: Richard Hartman <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, June 17, 1999 4:34 PM
> Subject: RE: DmFindRecordByID
>
>
> > I would really, really like to encourage Palm
> > to take out some of their automatic error dialogs
> > and let us have an API that really allows us to
> > check conditions. If we're calling a function
> > that's supposed to check on whether something
> > is ok or not, I expect that function to check
> > whatever it is and return the status to me so I
> > can take appropriate action. Period. The action
> > that Palm decides is what should happen may not
> > be what I want to happen.
> >
> >
> >
> > --
> > -Richard M. Hartman
> > [EMAIL PROTECTED]
> >
> > 186,000 mi./sec ... not just a good idea, it's the LAW!
> >
> >
> > > -----Original Message-----
> > > From: Ion Popescu [mailto:[EMAIL PROTECTED]]
> > > Sent: Thursday, June 17, 1999 11:40 AM
> > > To: [EMAIL PROTECTED]
> > > Subject: DmFindRecordByID
> > >
> > >
> > > Hi,
> > >
> > > In the new documentation (Reference.pdf) for DmFindRecordByID,
> > > it says that this function "May display a fatal error message
> > > if the unique ID is invalid.". What does this mean? I want to
> > > use this function to check if the unique id I have is valid
> > > (i.e to find out if the record with a particular uid
> > > still exists). If not, is there any other function/method I can
> > > use to check the existence of a record?
> > >
> > > Any help is appreciated.
> > >
> >
>
>
