Hi all,
I wanted to get a 5.2 snapshot for windows but noticed the it did not build.
The error in the log is:
ext\com_dotnet\com_extension.c(195) : error C2198:
'zend_exception_get_default' : too few actual parameters
Can anyone fix it so I can test the fixed __toString behaviour?
On Wed, 10 May 2006 18:46:43 +0300
manchokapitancho@gmail.com ("Marian Kostadinov") wrote:
Hi all,
I wanted to get a 5.2 snapshot for windows but noticed the it did not
build. The error in the log is:ext\com_dotnet\com_extension.c(195) : error C2198:
'zend_exception_get_default' : too few actual parametersCan anyone fix it so I can test the fixed __toString behaviour?
Rob fixed this error earlier today, the next snapshots should work.
-- Pierre
Thanks for the information. Finally I downloaded a new version and
__toString is working as expected.
There is an issue about error_reporting setting in php.ini. I took my php
5.1 php.ini file and used it for 5.2. Strangely it seemed that E_STRICT
suddenly turned on.
Is this an intended change or a bug?
2006/5/10, Pierre pierre.dev@gmail.com:
On Wed, 10 May 2006 18:46:43 +0300
manchokapitancho@gmail.com ("Marian Kostadinov") wrote:Hi all,
I wanted to get a 5.2 snapshot for windows but noticed the it did not
build. The error in the log is:ext\com_dotnet\com_extension.c(195) : error C2198:
'zend_exception_get_default' : too few actual parametersCan anyone fix it so I can test the fixed __toString behaviour?
Rob fixed this error earlier today, the next snapshots should work.
-- Pierre
There is an issue about error_reporting setting in php.ini. I took my php
5.1 php.ini file and used it for 5.2. Strangely it seemed thatE_STRICT
suddenly turned on.
Is this an intended change or a bug?
E_STRICT and E_RECOVERABLE_ERROR are now part of E_ALL
-Hannes
Marian Kostadinov wrote:
There is an issue about error_reporting setting in php.ini. I took my php
5.1 php.ini file and used it for 5.2. Strangely it seemed thatE_STRICT
suddenly turned on.
Is this an intended change or a bug?
AFAIK it was intended to change E_ALL to include E_STRICT in 5.2+
So you might like to change error reporting to something like E_ALL &
~E_STRICT in order to restore the old behavior.
-- Bastian
Marian Kostadinov wrote:
There is an issue about error_reporting setting in php.ini. I took
my php
5.1 php.ini file and used it for 5.2. Strangely it seemed that
E_STRICT
suddenly turned on.
Is this an intended change or a bug?AFAIK it was intended to change
E_ALLto includeE_STRICTin 5.2+
I think this was planned for PHP 6 not PHP 5.2. Although I don't see
a problem with making this change in 5.2 as well, does anyone have
any objections?
Ilia Alshanetsky
Advanced Internet Designs Inc.
ilia@prohost.org
On Fri, 12 May 2006 10:17:23 -0400
ilia@prohost.org (Ilia Alshanetsky) wrote:
Marian Kostadinov wrote:
There is an issue about error_reporting setting in php.ini. I
took my php
5.1 php.ini file and used it for 5.2. Strangely it seemed that
E_STRICT
suddenly turned on.
Is this an intended change or a bug?AFAIK it was intended to change
E_ALLto includeE_STRICTin 5.2+I think this was planned for PHP 6 not PHP 5.2. Although I don't see
a problem with making this change in 5.2 as well, does anyone have
any objections?
Yes, I do not think it is wise to do it. Something quiet using E_ALL in
5.x must remain quiet using 5.2.
However, there is maybe some edge cases where it makes sense. I do not
have any in mind.
-- Pierre
Hello Pierre, hello Ilia,
adding E_STRICT was an oversight from me. However we must have E_STRICT to
be able to inform our user base about changes removals in upcoming version.
That was decided upon in the PDM iirc.
best regards
marcus
p.s.: this is a new version with some additions and changes as has always
been with minor version in php. If we hadn't changes we would call it 5.1.5.
Friday, May 12, 2006, 4:25:42 PM, you wrote:
On Fri, 12 May 2006 10:17:23 -0400
ilia@prohost.org (Ilia Alshanetsky) wrote:
Marian Kostadinov wrote:
There is an issue about error_reporting setting in php.ini. I
took my php
5.1 php.ini file and used it for 5.2. Strangely it seemed that
E_STRICT
suddenly turned on.
Is this an intended change or a bug?AFAIK it was intended to change
E_ALLto includeE_STRICTin 5.2+I think this was planned for PHP 6 not PHP 5.2. Although I don't see
a problem with making this change in 5.2 as well, does anyone have
any objections?
Yes, I do not think it is wise to do it. Something quiet using
E_ALLin
5.x must remain quiet using 5.2.
However, there is maybe some edge cases where it makes sense. I do not
have any in mind.
Best regards,
Marcus