Post Reply 
HP49-50G: help for "frozen" screen
02-01-2024, 04:17 PM (This post was last modified: 02-01-2024 04:23 PM by DavidM.)
Post: #4
RE: HP49-50G: help for "frozen" screen
(02-01-2024 03:40 PM)Gil Wrote:  Nicely thought and found.

Thanks for your quick answer and solution.

Playing with your condition, it seems that
IFERR 1 DOERR THEN END
works.

But also IFERR DOERR THEN END

Regards

Any number or string should work, but numbers in the 0 - 9 range will take up less room. An empty string works as well.

I like 0 more than 1, only because 1 is a real error ("Insufficient Memory"), and if you subsequently use ERRN or ERRM, you will see what appears to be a legitimate error number or message.

The same applies to DOERR by itself, because it tries to use whatever is already in SL1 as its argument. If you happened to have a number or string in SL1 when calling DOERR, then that stack object will be "eaten" by DOERR, which is not likely what you want to happen. In other cases, ERRN and ERRM will then represent the error code #202h for "Bad Argument Type". That could be very misleading depending on how you troubleshoot.
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
HP49-50G: help for "frozen" screen - Gil - 02-01-2024, 10:52 AM
RE: HP49-50G: help for "frozen" screen - DavidM - 02-01-2024 04:17 PM



User(s) browsing this thread: 1 Guest(s)