>> As you 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,
>> where lines need to be split up in order to be easily readable. (Therefore
>> newline characters are par
On Sun, Aug 2, 2009 at 1:47 PM, Rony G.
Flatscher wrote:
> In order to figure out what I have been seeing ('?' for newline chars), I
> was able to trace this down to where the interpreter reports an error and
> the supplied error string contains a newline char. E.g.
>
> errorString="This is an err
Hi Mark,
> This is surely due to whatever you are using to "display" your string.
> Using the same Rexx code as in my other post, here is what I get:
>
... cut ...
> Which is exactly correct. This is the C++ code:
>
... cut ...
Again, thank you very much for looking into it. Went back into
On Sat, Aug 1, 2009 at 8:16 AM, Rony G.
Flatscher wrote:
> If a some const *char string contains the LF character (\n, 0x0a, 0d10)
> and one uses CString(str) to create a Rexx string, then say'ing that
> Rexx string would not cause a line break at the \n-character, rather a
> question mark (?) is
If a some const *char string contains the LF character (\n, 0x0a, 0d10)
and one uses CString(str) to create a Rexx string, then say'ing that
Rexx string would not cause a line break at the \n-character, rather a
question mark (?) is displayed instead. [At the same time a TAB char
(\t, 0x09, 0d09) r
