<feed xmlns='http://www.w3.org/2005/Atom'>
<title>delta/php-git.git/sapi/cli/cli_win32.c, branch php-5.6.26</title>
<subtitle>git.php.net: repository/php-src.git
</subtitle>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/php-git.git/'/>
<entry>
<title>Add optional php-win.exe variation of the CLI sapi.</title>
<updated>2004-01-14T03:14:18+00:00</updated>
<author>
<name>Wez Furlong</name>
<email>wez@php.net</email>
</author>
<published>2004-01-14T03:14:18+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/php-git.git/commit/?id=31f7699a857534d24990b1c7d5e06ed81e85ad9b'/>
<id>31f7699a857534d24990b1c7d5e06ed81e85ad9b</id>
<content type='text'>
php-win.exe runs in the windows GUI subsystem, and thus
has no console; stdio handles are effectively set to /dev/null
and no "dos box" will appear on screen when running scripts
using this sapi (php-gtk people will be familiar with this concept).

Aside from those differences, php-win.exe is 100% identical to
regular CLI

</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
php-win.exe runs in the windows GUI subsystem, and thus
has no console; stdio handles are effectively set to /dev/null
and no "dos box" will appear on screen when running scripts
using this sapi (php-gtk people will be familiar with this concept).

Aside from those differences, php-win.exe is 100% identical to
regular CLI

</pre>
</div>
</content>
</entry>
</feed>
