On Mon, October 30, 2006 7:19 pm, Daevid Vincent wrote:
> Thank you for the reply Richard (and Tom).
>
> That news sucks however. Seems that the PHP pre-parser should handle
> this
> better. It's not like it's a one-pass parser (like Ruby).
>
> <?php
> ini_set('output_handler', 'mb_output_handler');
> echo "\noutput_handler => " . ini_get('output_handler') . "\n";
> ?>
>
> I suppose I could re-compile my command line version with a different
> php.ini file, but that's kind of lame that I have to have two php.ini
> files
> for what ini_set() SHOULD handle.
There is nothing to "re-compile" here.
The command line has an existing flag for you to specify the php.ini
file, or to override any setting[s] within the php.ini file.
> What other undocumented "gotchas" are there with ini_set() I wonder...
Most of these ARE documented in that PER INI DIR page on php.net
This one probably is as well.
Bottom line, you can't step in the same river twice, and if php.ini
tells PHP to set up an ob_* handler before your script runs, it's
impossible to "undo" that just because you changed a setting that's
already been acted upon.
--
Some people have a "gift" link here.
Know what I want?
I want you to buy a CD from some starving artist.
http://cdbaby.com/browse/from/lynch
Yeah, I get a buck. So?
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
