Re: [Oorexx-devel] Question 1 ad CString(): not leaving \n untouched?
>> 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 error message.) >> >> As far as I recall this was not the case with 3.2 or earlier versions of >> ooRexx, such that I will file a bug for it. >> > > You should try it on 3.2 or earlier. My recollection is that it has > always been this way. Because I have tried in the past to put new > lines in error messages. > > If it has always been this way, then you would need to open an > enhancement instead of a bug. (My memory is not always the best > however.) > Hmm, already filed a bug. Will try it on 3.2 to be sure and may reclassify it to a RFE instead. ---rony -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Question 1 ad CString(): not leaving \n untouched?
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 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 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 error message.)
>
> As far as I recall this was not the case with 3.2 or earlier versions of
> ooRexx, such that I will file a bug for it.
You should try it on 3.2 or earlier. My recollection is that it has
always been this way. Because I have tried in the past to put new
lines in error messages.
If it has always been this way, then you would need to open an
enhancement instead of a bug. (My memory is not always the best
however.)
--
Mark Miesfeld
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Question 1 ad CString(): not leaving \n untouched?
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
native code and executing SAY-statements via it, and the newline worked!
---
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 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 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 error message.)
As far as I recall this was not the case with 3.2 or earlier versions of
ooRexx, such that I will file a bug for it.
Regards,
---rony
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Question 2 ad CString(): not leaving UTF chars untouched ?
Hi Mark, first of all: thank you *very* much for your efforts and describing your findings! Just was able to come back to my problem and in the light of your findings explicitly testing the conversion from const char string to a RexxString and vice-versa, and indeed it seems that the round trip works, so indeed all chars remain untouched! ---rony -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] ooRexx DOC build env
On Sun, Aug 2, 2009 at 2:14 AM, Rainer Tammer wrote: > I am checking the possibility to setup en build environment for the > ooRexx DOCs on AIX. > > Which _exact_ versions of the build tools are currently used ?? > > >From README.txt > * DocBook >= 4.2 > * OpenJade >= 1.3.2 > * TeX >= 7.4.5 with passivetex installed Rainer, I never paid attention to the versions. On Linux I just installed the latest versions available at the time, and everything seemed to work. -- Mark Miesfeld -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] recent changes to TRUNK break socket samples
On Sun, Aug 2, 2009 at 7:20 AM, Rainer Tammer wrote: > # ./sfserver.rex > 90 *-* if sockbind(socket, 'host.!') < 0 > 44 *-* srv~listen() > REX0040E: Error 40: Incorrect call to routine > REX0702E: Error 40.919: Argument 2 must have a stem object or stem name > value; found "host.!" > > The problem can be solved by changing "host.!xxx" to "host.xxx". > Is this intended ?? I doubt that Rick intended to break existing code. He probably intended the new code to make it easier on the user, and wasn't aware, or had forgotten, that the documentation advised the user to always use the stem name in the form: name.! Because of the doc, the change is sure to break a lot of people's existing programs. I'm sure Rick will fix when he gets a chance. -- Mark Miesfeld -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
[Oorexx-devel] recent changes to TRUNK break socket samples
Hello, # ./sfserver.rex 90 *-* if sockbind(socket, 'host.!') < 0 44 *-* srv~listen() REX0040E: Error 40: Incorrect call to routine REX0702E: Error 40.919: Argument 2 must have a stem object or stem name value; found "host.!" The problem can be solved by changing "host.!xxx" to "host.xxx". Is this intended ?? Bye Rainer -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
[Oorexx-devel] ooRexx DOC build env
Hello, I am checking the possibility to setup en build environment for the ooRexx DOCs on AIX. Which _exact_ versions of the build tools are currently used ?? >From README.txt * DocBook >= 4.2 * OpenJade >= 1.3.2 * TeX >= 7.4.5 with passivetex installed Especially TeX gives me a headache. I thought that the version number of TeX converges to pi. So how can TeX have 7.4.5 as version number? Bye Rainer Index: unix.sgml === --- unix.sgml (revision 5039) +++ unix.sgml (working copy) @@ -54,14 +54,11 @@ platform. - Any system capable of running AIX 5L 5.3 / AIX 6.1 for an AIX platform + Any system capable of running AIX 5L 5.2/5.3 or AIX 6.1 for an AIX platform. - Power 4 processor or higher for a PPC platform + Sparc processor for a SUN Solaris (Sparc) platform. - - Sparc processor for a SUN Solaris (Sparc) platform - @@ -233,7 +230,7 @@ - Required xlC runtime level + Required xlC.rte runtime level @@ -258,8 +255,9 @@ Installed services - The ooRexx 4.0.0.0 LPP will install the rxapi daemon. This daemon - is started automatically after the installation. The daemon will be started upon system boot via an + The ooRexx 4.0.0.0 LPP will install the rxapi daemon. This package + integrates seamlessly into the AIX SRC (System Resource Controller). The daemon is started + automatically after the installation. The daemon will be started upon system boot via an entry in /etc/inittab. @@ -275,7 +273,7 @@ - To install or remove the bff package, use smitty. + To install the LPP package, use smitty. + + + To remove the LPP package, use smitty. + + + + + + Installation of the TGZ Package Index: readme.sgml === --- readme.sgml (revision 5039) +++ readme.sgml (working copy) @@ -182,6 +182,8 @@ C:\work.ooRexx> ]]> + + On Linux, the following can be used from the command line: + + + If rxapi is not installed as a service, it can be stopped by using an appropriate process killer for your platform. Typically the Task Manager on Windows and kill on a unix-like system. -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
