Just finished updating to the latest sandbox revision - 11426 - and
attempted a 32-bit Windows build. The following errors were posted when
compiling SystemCommands.cpp:
E:\Sandbox\interpreter\platform\windows\SystemCommands.cpp(179): error
C2065: 'Error_Execution_address_redirection_failed': undeclared identifier
E:\Sandbox\interpreter\platform\windows\SystemCommands.cpp(518): error
C2039: 'waitForTermination': is not a member of 'ErrorReaderThread'
E:\Sandbox\interpreter\platform\windows\SystemCommands.cpp(104): note:
see declaration of 'ErrorReaderThread'
E:\Sandbox\interpreter\platform\windows\SystemCommands.cpp(526): warning
C4800: 'RexxObjectPtr': forcing value to bool 'true' or 'false'
(performance warning)
E:\Sandbox\interpreter\platform\windows\SystemCommands.cpp(533): error
C2039: 'waitForTermination': is not a member of 'InputWriterThread'
E:\Sandbox\interpreter\platform\windows\SystemCommands.cpp(75): note:
see declaration of 'InputWriterThread'
E:\Sandbox\interpreter\platform\windows\SystemCommands.cpp(537): warning
C4800: 'RexxObjectPtr': forcing value to bool 'true' or 'false'
(performance warning)
NMAKE : fatal error U1077: 'C:\PROGRA~2\MICROS~1.0\VC\bin\cl.exe' :
return code '0x2'
Stop.
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual
Studio 14.0\VC\BIN\nmake.exe"' : return code '0x2'
Stop.
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual
Studio 14.0\VC\BIN\nmake.exe"' : return code '0x2'
Stop.
Hope these messages are helpful...
Gil
On 4/20/2018 7:19 AM, Rick McGuire wrote:
Right now, monitor objects would not work (an oversight on my part).
I'll look into adding them. Output should be easy. Input is sort of
implicitly supported because the last step is to send a makeArray to
the object.
The reads from the pipes are done a buffer at a time and the error
output that is read on the separate thread needs to be buffered until
the process terminates, so no, they do not happen in real time.
Rick
On Fri, Apr 20, 2018 at 7:11 AM, Rony G. Flatscher
<rony.flatsc...@wu.ac.at <mailto:rony.flatsc...@wu.ac.at>> wrote:
On 19.04.2018 19:21, Erich Steinböck wrote:
> I just committed the Unix implementation of a redirecting system command
handler, that
passes all
> tests in (an updated) ADDRESS.testGroup.
>
> It handles OUTPUT in the main thread, and INPUT and ERROR in
additional threads when required.
> (Handling OUTPUT in the main thread will allow Rexx code to get
concurrent progress information
> for long running commands; ERROR information becomes available
only after the ERROR thread ends).
How about, if one supplies monitor objects to be used (e.g. one
for STDIN, one for STDOUT and one
for STDERR)? Would they get messages dispatched in "real-time"
from the different threads? If so
this would allow for e.g. timestamping or analysis of the item
flows via the different standard
files and the like.
---rony
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
<mailto:Oorexx-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
<https://lists.sourceforge.net/lists/listinfo/oorexx-devel>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org!http://sdm.link/slashdot
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
--
Gil Barmwater
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
