> Some 64bit issues, some bugs marked "Critical", etc..
>
On the 64bit issues... other than the ext/mbstring thing I am not
currently aware of any. I am still looking at the current test
failures though - I have 12 and so far 3 are explainable do to os
"features" and one is the mbstring pro
On Tue, 18 Mar 2003, Marcus Börger wrote:
>At 16:30 18.03.2003, Jani Taskinen wrote:
>>On Sun, 16 Mar 2003, Marcus Börger wrote:
>>
>> >But from my point of view the only thing to do is fix bug 21007.
>>
>> So are you fixing it?
>>
>
>Yeah i'll add something to PG() and set it different from
>
At 16:30 18.03.2003, Jani Taskinen wrote:
On Sun, 16 Mar 2003, Marcus Börger wrote:
>But from my point of view the only thing to do is fix bug 21007.
So are you fixing it?
Yeah i'll add something to PG() and set it different from
CLI and blabla...ok? What's my timeframe for the 4.3.2
or do
On Sun, 16 Mar 2003, Marcus Börger wrote:
>But from my point of view the only thing to do is fix bug 21007.
So are you fixing it?
--Jani
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
is it worth make the default use something like the PHPID=. to point
to a short note saying - modify your php.ini configuration file to
enable docref links. - PLEASE DO NOT DO THIS ON PRODUCTION BOX's
otherwise we will come round with the lart...
Regards
Alan
Marcus Börger wrote:
Hi all
I
Hi all
I have changed the default ini value for html_errors to 0.
I think default ini settings should work for production boxes and noone should
have html_errors=On for those.
The second thing i changed is that errors are no longer pointing to any
documentation if either html_erros=0 or docref_ro
