#367 Newline chars in error messages should remain intact

[Rony G. Flatscher]

The following Rexx program contains a newline char in its error message.

errorString="This is an error" || "0a"x || "and this the second line of that error."
raise syntax 98.900 array (errorString)

Running the above Rexx program then yields:

E:\test>makeError.rex
     3 *-* raise syntax 98.900 array (errorString)
Error 98 running E:\test\makeError.rex line 3:  Execution error
Error 98.900:  This is an error?and this the second line of that error.

As one can see the line reading "Error 98.900" displays '?' instead of breaking the line at that position.

The BSF4Rexx support will create rather well documented error messages (to ease error spotting in a potentially complex environment), where lines need to be split up in order to be easily readable. Therefore newline characters are part of the error message.

This RFE requests that newline chars in error message string remain intact and do not get replaced by a question mark.