Re: [Oorexx-devel] CMS/TSO Pipelines support for Rexx

2009-05-12 Thread Rony G. Flatscher
James, please lookup rexxpg.pdf, chapter 9, Rexx C++ Application Programming Interfaces. There you will find the C++ APIs documented, and among the documentation you will find the new options and there the option named DIRECT_ENVIRONMENTS which supplies a context for the purpose you need.

Re: [Oorexx-devel] CMS/TSO Pipelines support for Rexx

2009-05-12 Thread Rick McGuire
James, The legacy-style APIs are being retired and will not be enhanced in the future. That API was one designed over 20 years ago specifically for OS/2 and unfortunately got propagated as standard which it was never intended to be. New APIs will be based on the API system. The other bad news

[Oorexx-devel] Inconsistency in stream~arrayout() / arrayin()

2009-05-12 Thread Mark Miesfeld
In the stream methods arrayout and arrayin where you can specify CHARS or LINES, there is an inconsistency with most other methods in ooRexx, in that the argument is case sensitive. You can specify 'C', but not 'c'. You can specify LINES but not lines. It is not documented one way or the other

Re: [Oorexx-devel] Inconsistency in stream~arrayout() / arrayin()

2009-05-12 Thread Rick McGuire
Even using Abbrev() is inconsistent with other Rexx option usage. It really only look at the first character (in a caseless manner, of course). I think this should be changed. Rick On Tue, May 12, 2009 at 12:23 PM, Mark Miesfeld miesf...@gmail.com wrote: In the stream methods arrayout and

Re: [Oorexx-devel] Inconsistency in stream~arrayout() / arrayin()

2009-05-12 Thread Mark Miesfeld
On Tue, May 12, 2009 at 9:28 AM, Rick McGuire object.r...@gmail.com wrote: Even using Abbrev() is inconsistent with other Rexx option usage.  It really only look at the first character (in a caseless manner, of course). I think this should be changed. Okay, I'll change that. -- Mark

[Oorexx-devel] stream~supplier bug?

2009-05-12 Thread Mark Miesfeld
In the documentation for .Stream~supplier, it says: Returns a Supplier object for the stream containing the remaining stream lines and linenumber positions for the stream. Containing the *remaining stream lines, led me to expect that after reading 3 lines of a 18 line file, and then getting a

Re: [Oorexx-devel] stream~supplier bug?

2009-05-12 Thread Rick McGuire
Well, your expectation certainly matches mine. I don't believe the implementation of this has been touched in any of the releases, so it might very well be buggy. Rick On Tue, May 12, 2009 at 2:27 PM, Mark Miesfeld miesf...@gmail.com wrote: In the documentation for .Stream~supplier, it says:

Re: [Oorexx-devel] stream~supplier bug?

2009-05-12 Thread Rick McGuire
I might also add that the bug you see in the 3.2.0 version was introduced right before 3.2.0 shipped. Given that nobody has opened a bug report against this, I suspect we can probably fix how this works without breaking many programs :-) I suspect the most difficult part will be ensuring that

Re: [Oorexx-devel] stream~supplier bug?

2009-05-12 Thread Mark Miesfeld
On Tue, May 12, 2009 at 11:34 AM, Rick McGuire object.r...@gmail.com wrote: I might also add that the bug you see in the 3.2.0 version was introduced right before 3.2.0 shipped.  Given that nobody has opened a bug report against this, I suspect we can probably fix how this works without

Re: [Oorexx-devel] stream~supplier bug?

2009-05-12 Thread Rick McGuire
Sure...though the code for the supplier is written entirely in ooRexx code if you'd like to try tackling this one. The code is in StreamClasses.orx. Rick On Tue, May 12, 2009 at 2:38 PM, Mark Miesfeld miesf...@gmail.com wrote: On Tue, May 12, 2009 at 11:34 AM, Rick McGuire

Re: [Oorexx-devel] stream~supplier bug?

2009-05-12 Thread Mark Miesfeld
On Tue, May 12, 2009 at 11:44 AM, Rick McGuire object.r...@gmail.com wrote: Sure...though the code for the supplier is written entirely in ooRexx code if you'd like to try tackling this one.  The code is in StreamClasses.orx. Okay, I'll do this one. -- Mark Miesfeld