newRPL - Updated to build 1510 [official build remains at 1487]

[JoJo1973]

(09-09-2021 03:47 PM)Claudio L. Wrote:  

(09-09-2021 07:49 AM)JoJo1973 Wrote:  ARGCK could accept a third parameter:

0: Bad type/count error
Integer: Issue corresponding error
String: DOERR
Program/Identifier: Error handler

OK, so let's get organized:
The commands would be then 2 separate ones:

Code:


<arg # (stack level)> <List of valid types> CKARG
<arg # (stack level)> <List of valid types> <Error/Message> CKARGERR

Where the <Error/Message> parameter can be as you described above.

CKARG would return the POS of the item that matches, or 0 if no match. No error is thrown.
CKARGERR returns the POS of the item, otherwise throws the given error message (or XEQ the handler).
Now there's 2 possible error conditions:
a) If the stack is not deep enough ---> issues a "Bad Argument Count" error, it does NOT run the handler or use the given message
b) If there's no match ---> Custom message / XEQ error handler

Are we good with this? I think specs are pretty much finished, let's agree on names and I can get coding.

Sure, Bad Argument Count should have the precedence.