Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!bridge2!jarthur!sburke
From: sburke@jarthur.Claremont.EDU (Scott Burke)
Newsgroups: comp.sys.handhelds
Subject: Re: 48 Errors
Message-ID: <11938@jarthur.Claremont.EDU>
Date: 29 Apr 91 11:23:12 GMT
References: <11898@jarthur.Claremont.EDU> <15360@helios.TAMU.EDU> <281b0c9e:2931.2comp.sys.handhelds;1@hpcvbbs.UUCP>
Organization: Harvey Mudd College, Claremont, CA 91711
Lines: 18

Hi.

Aaron's follow-up article on error messages is helpful.  However, that is a
method I've already implemented, and it does faithfully duplicate _nearly_
all error messages.  Here's the difficult case:

You write a user-defined function that takes an argument off the stack.  In
that user-defined function, the first command MUST be \-> varname.  There is
NO way to start with an IFERR or anything else, so you can't trap the \->
error that occurs if there are no arguments on the stack, so that you can
replace the "\-> Error:" line with "Custom Error:".

Give this one a try in user-RPL?  I don't think it's possible.  After a brief
discussion with Rick, it doesn't seem to be solvable by any small amount of
effort if you prefer to remain in user-RPL-land, which I do.

Scott.
sburke@jarthur.claremont.edu