Re: [INTERNALS-WIN] Advice for enhancing ext/standard/proc_open.c (Windows CLI only)

From: Date: Sat, 21 Aug 2010 11:54:58 +0000
Subject: Re: [INTERNALS-WIN] Advice for enhancing ext/standard/proc_open.c (Windows CLI only)
References: 1 2  Groups: php.internals.win 
Request: Send a blank email to internals-win+get-714@lists.php.net to get a copy of this message
What's the goal of this patch exactly? Avoid the creation of the console window?
Basically yes...the patch stops the presentation of an empty console window. I am trying to support a script that can make dozens of calls to proc_open. Without this patch, each call presents an empty, unresponsive console box for the duration of the created process.
However the patch looks wrong. It kills the bypass shell option, which is not something we like to do.
It certainly doesn't intend to kill the bypass_shell option. In fact, the functionality in this patch requires that the bypass_shell option be set. AFAIK, the bypass_shell option should continue to work normally. Why do you think that the patch kills the bypass_shell option? - Eric, http://noteworthysoftware.com

« previous php.internals.win (#714) next »