Re: [Oorexx-devel] Question 1 ad CString(): not leaving \n untouched?

2009-08-02 Thread Rony G. Flatscher
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 the

Re: [Oorexx-devel] Question 1 ad CString(): not leaving \n untouched?

2009-08-02 Thread Mark Miesfeld
On Sun, Aug 2, 2009 at 1:47 PM, Rony G. Flatscherrony.flatsc...@wu-wien.ac.at 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.

Re: [Oorexx-devel] Question 1 ad CString(): not leaving \n untouched?

2009-08-02 Thread Rony G. Flatscher
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 part of the

[Oorexx-devel] Question 1 ad CString(): not leaving \n untouched?

2009-08-01 Thread Rony G. Flatscher
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)

Re: [Oorexx-devel] Question 1 ad CString(): not leaving \n untouched?

2009-08-01 Thread Mark Miesfeld
On Sat, Aug 1, 2009 at 8:16 AM, Rony G. Flatscherrony.flatsc...@wu-wien.ac.at 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