Process in Win32
Posted: Sat Jan 07, 2006 10:06 pm
Hi Lutz,
As of 8.7.5 there is new functionality in the 'process' statement: the stderr is redirected by default to stdout.
This creates a problem when communicating by 2-way pipes. It means that errors caused by the child process disturb the regular communication. My GTK-server does not show the GTK GUI anymore, when GTK errors happen disturbing the channel.
For Linux/Unix I can redirect stderr to a 3rd pipe. However, according to the docs this is not possible for Win32.
It means it would break all compatibility in situations where newLisp wants to communicate with a child process, and this child process generates errors.
For the GTK-server this can be solved by importing the DLL version now. But for other situations I guess there is a problem.
Is there a way to implement this 3rd pipe for stdout also for Win32?
Peter
As of 8.7.5 there is new functionality in the 'process' statement: the stderr is redirected by default to stdout.
This creates a problem when communicating by 2-way pipes. It means that errors caused by the child process disturb the regular communication. My GTK-server does not show the GTK GUI anymore, when GTK errors happen disturbing the channel.
For Linux/Unix I can redirect stderr to a 3rd pipe. However, according to the docs this is not possible for Win32.
It means it would break all compatibility in situations where newLisp wants to communicate with a child process, and this child process generates errors.
For the GTK-server this can be solved by importing the DLL version now. But for other situations I guess there is a problem.
Is there a way to implement this 3rd pipe for stdout also for Win32?
Peter