Re: [Oorexx-devel] Discussion: Do I have the correct Write methods in the APIs.

2018-04-04 Thread Rick McGuire
Sourceforge is still having SVN issues, so the code is not checked in yet, but I've added WriteOutputBuffer() and WriteErrorBuffer() to the API vector. You should be able to read a buffer of data from the pipe and write it out without having to worry about any linends. Rick On Wed, Apr 4, 2018

Re: [Oorexx-devel] Address With progress

2018-04-04 Thread Erich Steinböck
>From the description in https://blog.uxul.de/e?e=mt-160 (very bottom) it seems "trivial" to do. Not a Linux guru at all, but I'd give it a try if no one else volunteers. The blog also contains a discussion of an interesting quirk with fork(), which is why the sample code uses POSIX spawn to

[Oorexx-devel] Address With progress

2018-04-04 Thread Rick McGuire
I still have to write a bunch of unit tests for the global Address With setup and overrides, but all of the base redirection mechanisms are now passing the unit tests. The missing piece right now is the redirection in the system handlers. Any Linux gurus out there willing to take a look at how to

[Oorexx-devel] Discussion: Do I have the correct Write methods in the APIs.

2018-04-04 Thread Rick McGuire
Now that I've gotten all of these mechanisms working, I'm starting to think we might need a little more. My thinking to this point is that the WriteOutput() and WriteError() calls are line-at-a-time operations. But I realized that the handler might be reading larger buffers of data composed of

Re: [Oorexx-devel] Discussion: Do I have the correct Write methods in the APIs.

2018-04-04 Thread Gil Barmwater
Yes, I ran into this issue when developing my package.  I had assumed that there was an equivalent to Linein() and Lineout() in Windows so I made my interface to the C++ code a set of three arrays, one each for INPUT, OUTPUT and ERROR.  When I got to actually implementing that part, I

Re: [Oorexx-devel] Discussion: Do I have the correct Write methods in the APIs.

2018-04-04 Thread Rick McGuire
On Wed, Apr 4, 2018 at 11:14 AM, Gil Barmwater wrote: > Yes, I ran into this issue when developing my package. I had assumed that > there was an equivalent to Linein() and Lineout() in Windows so I made my > interface to the C++ code a set of three arrays, one each for

Re: [Oorexx-devel] Comments and discussion about ADDRESS WITH

2018-04-04 Thread Erich Steinböck
On Ubuntu gcc, I'm receiving below compile error. Compile runs fine if I remove "LineinInvoker::" .. didn't yet check if with this modification compile runs still fine on Windows ~~~ [ 13%] Building CXX object CMakeFiles/rexx.dir/interpreter/instructions/InputRedirector.cpp.o

Re: [Oorexx-devel] Comments and discussion about ADDRESS WITH

2018-04-04 Thread Rick McGuire
Oops, no that is the correct fix. Trying to commit some changes right now but sourceforge is still having issues. Rick On Wed, Apr 4, 2018 at 4:39 PM, Erich Steinböck wrote: > On Ubuntu gcc, I'm receiving below compile error. > Compile runs fine if I remove