At 20:58 03.05.2001 +0300, Andi Gutmans wrote:
>At 07:42 PM 5/3/2001 +0200, Daniel Beulshausen wrote:
>>At 19:24 03.05.2001 +0200, Daniel Beulshausen wrote:
>>>At 20:04 03.05.2001 +0300, Andi Gutmans wrote:
>>>>At 12:59 PM 5/3/2001 -0400, Joe Brown wrote:
>>>>>echo typically is not a program.
>>>>>It is a command in the CMD.exe or COMMAND.com programs.
>>>>>$output=exec("cmd -c echo hello"); //should produce the desired effect.
>>>>>Why piping output to a file changes this fact, is beyond me.
>>>>The definition of exec() is that it uses popen() which starts a shell
>>>>automatically. Anyway, the problem was very Windows specific and
>>>>doesn't have anything to do with the syntax he used.
>>>right now we are executing the programm direct, without creating a console.
>>>maybe we should manage a list of internal commands, like echo, dir,
>>>copy,... and create a console for them...
>>no it's a bad idea, i'll shut up :)
>>cmd line parsing is a pretty bad idea, and the user is better of doing
>>passthru( getenv("COMSPEC") . " /c echo")
>Ouch but then the fix isn't popen() compatible.
we could behave exactly like popen if we would check for COMSPEC, and if
that isn't present detect the OS and use command.com or cmd.exe, that's
exactly like MS is behaving.
but it would be a bad idea IMO, as server's could deny access to them
daniel beulshausen - [EMAIL PROTECTED]
using php on windows? http://www.php4win.de
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]