Status: New Owner: benoit.m...@gmail.com Labels: Version-3.5.0 Type-Bug Priority-Medium OpSys-Any Dist-Any Arch-Any Desktop-Any GUI-Any
New issue 499 by benoit.m...@gmail.com: Unable to parse the standard error stream if using "Shell ... For Input" instead of "Shell ... For Read" http://code.google.com/p/gambas/issues/detail?id=499 1) Describe the problem. I'm unable to parse the standard error stream if using "for input" instead of "for read". To explain better, this: -- Public myprocess As Process Public Sub Main() myprocess = Shell "/bin/ls /does/not/exist" For Input As "myprocess" End Public Sub myprocess_error(MyError As String) Print myerror End --- Does not produce any output. So, by now: If one wants to start an external command and redirect the standard output to a file: 1- using "FOR READ" makes the cpu jumps to 100% and the interpreter hangs on exit. 2- using "FOR INPUT" makes impossible to parse error messages in the stderr stream. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ Gambas-user mailing list Gambas-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gambas-user
