Looks like recent changes to array.c broke the build for 5.3:
line 4092 is:
zend_fcall_info fci = empty_fcall_info;
but empty_fcall_info doesn't seem to be defined anywhere. Please fix.
--
Stanislav Malyshev, Zend Software Architect
[EMAIL PROTECTED] http://www.zend.com/
(408)253-8829 MSN: [E
On Nov 7, 2007 7:18 PM, Stanislav Malyshev <[EMAIL PROTECTED]> wrote:
> Looks like recent changes to array.c broke the build for 5.3:
> line 4092 is:
> zend_fcall_info fci = empty_fcall_info;
> but empty_fcall_info doesn't seem to be defined anywhere. Please fix.
cvs up Zend
Checking out the "ph
Hannes Magnusson kirjoitti:
On Nov 7, 2007 7:18 PM, Stanislav Malyshev <[EMAIL PROTECTED]> wrote:
Looks like recent changes to array.c broke the build for 5.3:
line 4092 is:
zend_fcall_info fci = empty_fcall_info;
but empty_fcall_info doesn't seem to be defined anywhere. Please fix.
cvs up Ze
cvs up Zend
Checking out the "php5" pseudo module will safe you a lot of headaches
like this.
That's what I did, but for some reason my cvs decided to ignore Zend
changes... Sorry for false alarm.
--
Stanislav Malyshev, Zend Software Architect
[EMAIL PROTECTED] http://www.zend.com/
(408)253
The patch to implement multiple namespaces per file, and the patch to
remove keyword restrictions for methods appear to have fallen through
the cracks. I would like to encourage at the minimum a review, and
About the second - I'm not sure which patch it is, I remember there was
a simple one an
This is not an OSX specific issue, it's a symbol leakage issue that
can break potentially any library that uses that feature of gcc. I
just happened to notice it on OSX.
Better to rename our symbols to avoid conflict.
--Wez.
On Nov 7, 2007, at 2:48 AM, Dmitry Stogov wrote:
May be it is b
2007/11/7, Sriram Natarajan <[EMAIL PROTECTED]>:
> Hi
> Will you guys consider adding support for 'Include' file / directory
> support (like 'conf.d' in Apache HTTPd) so that extensions can be
> defined within a separate file rather than editing a single 'php.ini' ?
> I understand that some Linux
Hi
Will you guys consider adding support for 'Include' file / directory
support (like 'conf.d' in Apache HTTPd) so that extensions can be
defined within a separate file rather than editing a single 'php.ini' ?
I understand that some Linux distributions do this currently. But, I am
interested i
I have a bunch of php 6 tests which work when I run them in non-unicode
(php run-test.php -N test.phpt) and in unicode mode (php run-test.php -u
test.phpt) but the first test fails when I run it in "both" mode (php
run-test.php -U test.phpt). I thought if test passes -N and -u, it
should always