#1180 x2b/x2c/x2d Don't Accept Whitespace

4.1.3
closed
None
none
1
2014-11-07
2013-05-28
Erich
No

Here's another bug, this time for x2b/x2c/x2d (both method and BIF).

Docs say

x2b/x2c/x2d: "You can optionally include whitespace .. to improve readability; they are ignored."

Whitespace: "A whitespace character is one that the interpreter recognizes as a "blank" or "space" character. There are two characters used by Rexx as whitespace that can be used interchangably:
A "blank" or "space" character ..
A "tab". This is represented by ’09’X in ASCII implementations.

This code snippet shows that a tab (between 3131 and 3232) seems to be supported within a hex literal, but not by x2c():

Str='3131   3232'x
say Str
Str='3131   3232'
say x2c(Str)

ooRexx issues Error 93.933: Only 0-9, a-f, A-F, and whitespace characters are valid in a hexadecimal string; character found " "

Discussion

  • Mark Miesfeld

    Mark Miesfeld - 2013-05-28
    • assigned_to: Mark Miesfeld
     
  • Mark Miesfeld

    Mark Miesfeld - 2013-05-28
    • status: open --> pending
    • Group: 4.1.2 --> 4.1.3
     
  • Mark Miesfeld

    Mark Miesfeld - 2013-07-09
    • status: pending --> closed
     
  • Mark Miesfeld

    Mark Miesfeld - 2013-07-09

    This bug is fixed in the ooRexx 4.1.3 release.

     


Anonymous

Cancel  Add attachments