2023 RPN HHC Programming Contest

[Allen]

Craig,
Thank you for the interesting CC41 program and congrats on the solution at the conference! I really love the "load and run this program on start"!! On the face that seems really handy, and I was preparing to do on the computer what I've been doing by hand the last week or so, until...

There are a few small behaviors that are somewhat different than a normal 41C would do:

Code:

> pi     x: 3.1416 y:50.0000 z:0.0000 t:32.0000 l:50.0000 a:
> cos     x: 0.9985 y:50.0000 z:0.0000 t:32.0000 l:3.1416 a:
> isg x   x: 49.9985 y:50.0000 z:0.0000 t:32.0000 l:3.1416 a:
> dec   x: 40.0000 y:50.0000 z:0.0000 t:32.0000 l:49.9985 a:

(this is correct for input of 50.0000, but 49.9985 should say "DATA ERROR" and leave x value unchanged?)

or

Code:

> pi     x: 3.1416 y:0.0000 z:41.0000 t:50.0000 l:49.0000 a:
> cos     x: 0.9985 y:0.0000 z:41.0000 t:50.0000 l:3.1416 a:
> isg x     x: 49.9985 y:0.0000 z:41.0000 t:50.0000 l:3.1416 a:
> int     x: 49.0000 y:0.0000 z:41.0000 t:50.0000 l:49.9985 a:
> dec     x: 0.0000 y:0.0000 z:41.0000 t:50.0000 l:49.0000 a:

(0.00 is not a valid oct to dec conversion for anything except input of 0.000 . should say "DATA ERROR" and leave x value unchanged?)

Neither of these x values would be allowed without error checking the OCT->DEC command for integer input not containing the '9' digit in the base10 number. the DEC->OCT command does not have the numerical restriction, but should check for integer input.

Code:

> 5.5     x: 5.5000 y:0.0000 z:0.0000 t:41.0000 l:49.0000 a:
> oct     x: 6.0000 y:0.0000 z:0.0000 t:41.0000 l:5.5000 a:

should also return error and leave x value unchanged?

I confess I've only looked at it for a few minutes, so if this is something clearly addressed in the nicely written manual (which I did search for notes on OCT and DEC behaviors) , it is my own lack of reading and I apologize in advance.