Recent changes to bugs

#620 x2d implementation incomplete

Paul van den Eertwegh — Tue, 07 Apr 2026 15:02:54 -0000

The non-strict comparison first trims leading and trailing spaces of the arguments.
Thus the first one becomes (ascii 20 = space):
say "00"x>"" (empty string).

Then we have a compare of 2 strings with different lengths. According to the manual, the shorter one is padded with spaces until the length of the longer one. We should get:
say "00"x>" " (1 space). This should give 0!

Bug. ooRexx here gives the correct result.

Using the strict >> gives correct result.

#620 x2d implementation incomplete

Stefan Haubenthal — Fri, 03 Apr 2026 14:15:28 -0000

What about this

say "00"x>"20"x
1
say "00"x>"21"x
0

#621 TAN function 2 minor errors

J Watson — Wed, 25 Mar 2026 09:16:18 -0000

Yes

#621 TAN function 2 minor errors

Stefan Haubenthal — Tue, 24 Mar 2026 20:28:00 -0000

Are talking about regutil's systan?

#622 \-0

Ross Patterson — Mon, 23 Mar 2026 16:37:12 -0000

It's interesting that the lexer throws error 35.1 for the simple case ("-0"), but that it passes a more complex case, which evaluates correctly.

12 *-* say \(-0)
   >L>   "0"
   >P>   "0"
   >U>   "1"

TRL2 pp. 24 (emphasis mine) says:

Expressions consist of one or more terms (literal strings, symbols, function calls, or sub-expressions), and zero or more operators that denote operations to be carried out on terms. Most operators act on two terms, and there will be at least one of these dyadic operators between every pair ofterms. 17 There are also prefix (monadic) operators, that act on the term that is immediately to the right of the operator. There may be one or more prefix operators to the left of any term.

and ANSI 6.3.2.112 says:

prefix_expression := ('+' | '-' | '\') prefix_expression | term | Msg35.1

#622 \-0

Stefan Haubenthal — Mon, 23 Mar 2026 10:48:39 -0000

Hmm, Regina is simply "strict", so that's the way it is?

\-0

Stefan Haubenthal — Mon, 23 Mar 2026 09:13:38 -0000

say -\0
-1
say \-0
Error 35 running "<stdin>", line 1: Invalid expression
Error 35.1: Invalid expression detected at "\"

why? not and minus are legal prefixes

by the way the message doesn't mention "~"

say ~-0
Error 35 running "<stdin>", line 1: Invalid expression
Error 35.1: Invalid expression detected at "\"

TAN function 2 minor errors

J Watson — Sun, 15 Feb 2026 17:20:46 -0000

TAN() function gives an unexpected execution error if argument is +90, +270, -90 etc. It reports "Error 40 incorrect call". I'd argue that the call is correct but maybe the response should be clearer. It wouldn't be possible to return the correct value (+/- infinity) as this concept doesn't exist in REXX. For comparison, MS-Excel returns a crazy large number rather than fail - which I'd also disagree with! Unable to find out what the same IBM function does, but I suspect there's also an execution error

Also, the 3rd argument (unit= D, R, G) doesn't seem to work at all, always returning "0" if it's specified

#620 x2d implementation incomplete

Stefan Haubenthal — Wed, 12 Nov 2025 00:08:05 -0000

oops, it's EBCDIC

x2d implementation incomplete

Stefan Haubenthal — Tue, 11 Nov 2025 19:04:17 -0000

TRL2 p. 116 says

X2D('c6 f0'X) == 240

Take care of the X!