On Mon, Mar 25, 2002 at 09:44:00PM +0100, Edin Kadribasic wrote: > Are you sure you were testing it with CLI? Header hiding (-q) has been in > there since the first check-in back in Jan 6.
This is good. I have tried to compile a list of things I would like to see in php-cli, and haven't checked yet which of these are already there. I came up with - automatic -q mode enabled - php honoring -- as "end of options" as required by getopt so that "#! /usr/bin/php ... --" can be written and works as expected, even if somebody names his script "-i" or something. - no html in error messages or warnings - php reading /etc/php-cli.ini, $HOME/.php.ini unless $PHPRC suggests something different. ./.php.ini and ./php.ini not read, unless "." is put in $PHPRC path. - safe_mode'ish features off or even disabled, since they make no sense in cli. - gpc variables not registered, argc/argv honored - error logging to stderr, not to syslog or other target. - sensible php.ini default installed with no execution time limit and memory limit. This list is not complete, it is just what comes to mind immediately when thinking of cli-ifying php. Also, I wonder how starting PHP in HTML-mode relates to CLI usage, but I believe this would break to many things. ----- #! /usr/bin/php -- Hello world ----- "Hello world" program in php-cli, starting in HTML mode. ----- #! /usr/bin/php -- <?php echo "Hello world"; ----- The same, as of now, using actual PHP facilities ----- #! /usr/bin/php -- echo "Hello world"; ----- What someone would expect from a scripting language. Kristian -- Kristian Köhntopp, NetUSE AG, Dr.-Hell-Straße, D-24107 Kiel Tel: +49 431 386 435 00, Fax: +49 431 386 435 99 -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
