Marcus Boerger wrote:
> Hello internals,
>
> the attached patch introduces a new handler to the engine that is
> supposed to help debugging overloaded objects. It allows to return a
> temporary hash rather then the object properties. This way an extension
> can show non properties in var_dump()
Arnold Daniels wrote:
>if (ret != NULL) {
>printf('1');
>}
'1' is 0x0031, use "1" and you'll get a real memory address to print.
--
Michael
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Arnold Daniels wrote:
> I've got no idea where the the stands for.
PHPUnit reports progress with .FEIS characters, see
http://www.phpunit.de/pocket_guide/3.0/en/textui.html for details.
--
Sebastian Bergmann http://sebastian-bergmann.de/
GnuPG Key: 0xB85B5D69 / 27
PHP 5 Bug Database summary - http://bugs.php.net
Num Status Summary (626 total including feature requests)
===[*Compile Issues]==
39372 Suspended Incompatibility in the PHP API.
===[*Configur
On Mon, 15 Jan 2007, Marcus Boerger wrote:
> Any comments?
Shouldn't you init is_temp here? As far as I can see it is not initialized in
every code path, and there is an if() using it in the 3rd patch element here:
> @@ -581,6 +581,7 @@ ZEND_API void zend_print_zval_r_ex(zend_
>
the attached patch introduces a new handler to the engine that is
supposed to help debugging overloaded objects. It allows to return a
temporary hash rather then the object properties. This way an extension
can show non properties in var_dump() and print_r(). It will be used
in extensions like S
The solution I'm tempted to pursue for this is to back up yet another
step and make autoglobals be CVs by extending the zend_compiled_variable
struct to contain a flag indicating how the var should be fetched (the
determination for which happens during fetch_simple_var during the
compilation.
Hello internals,
the attached patch introduces a new handler to the engine that is
supposed to help debugging overloaded objects. It allows to return a
temporary hash rather then the object properties. This way an extension
can show non properties in var_dump() and print_r(). It will be used
in
Option 4:
Include fetchtype and subelement during runtime JIT callback allowing
JIT callback to only do work necessary to prepare for the read/write
call being performed.
e.g.
int php_example_jit_callback(int str_type, zstr str, int str_len,
int stage, zval *container, int fetch_type, zva
On Mon, 15 Jan 2007, Arnold Daniels wrote:
> Hi again,
>
> First of all thanks for your reply. It sound logical, but doesn't work
> unfortunately. I now get:
>
>seabert:/var/pear# phpunit Test_Standard_qconf
>PHPUnit 3.0.0alpha11 by Sebastian Bergmann.
>
>Segmentation fault
>
>
On 01/15/2007 11:03 PM, BuildSmart wrote:
PHP looks for "mail_append_set" im mail.h (which is present only in
new versions of c-client) and uses new utf8_mime2text() semantics
if it's present.
If you have BOTH "mail_append_set" and old "utf_mime2text()", then
it's likely you have some proble
Reinis Rozitis wrote:
p.s. lately the topics and discussions on internal list are pretty
scarry.. starting with political issues and ending with memory manager
flaws (besides also some phparchitect articles which propose/show 5.2
being faster in all generic tests still slower in realworld
apli
On 01/16/2007 12:12 AM, Arnold Daniels wrote:
Hi again,
First of all thanks for your reply. It sound logical, but doesn't work
unfortunately. I now get:
seabert:/var/pear# phpunit Test_Standard_qconf
PHPUnit 3.0.0alpha11 by Sebastian Bergmann.
Segmentation fault
I've got no
Hi again,
First of all thanks for your reply. It sound logical, but doesn't work
unfortunately. I now get:
seabert:/var/pear# phpunit Test_Standard_qconf
PHPUnit 3.0.0alpha11 by Sebastian Bergmann.
Segmentation fault
I've got no idea where the the stands for.
/**
* Parse .
On 01/15/2007 11:50 PM, Arnold Daniels wrote:
Hi,
I could use some help on an extension I've written. It worked fine
before, but from out the blue I started to get segmentation faults. I've
located it down to this piece of code, but I don't do any writes to the
code memory, so I don't get wha
Hi,
I could use some help on an extension I've written. It worked fine
before, but from out the blue I started to get segmentation faults. I've
located it down to this piece of code, but I don't do any writes to the
code memory, so I don't get what's wrong. It seems like the error lies
in the
Hello,
It seems that the EXPERIMENTAL file for ncurses was lost during the
migration of this module to PECL.
Was this change intentional? Can we lose the warnings in ncurses docs?
Thanks in advance
Mehdi
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://ww
No, no features will be back ported to PHP 4.4.
Although I dont see this as feature more like a fix (uneeded opens() stats()
on each call) still thank you for the fast reply.
p.s. lately the topics and discussions on internal list are pretty scarry..
starting with political issues and endin
On Mon, 15 Jan 2007, Reinis Rozitis wrote:
> Hello,
> just a quick question - will the include_once() (Optimized require_once() and
> include_once() by eliminating fopen(3) on second usage. (Dmitry)) optimisation
> fix in 5.2.0 backported also in PHP 4 tree (in 4.4.5 maybe?)
No, no features will
Hello,
just a quick question - will the include_once() (Optimized require_once()
and include_once() by eliminating fopen(3) on second usage. (Dmitry))
optimisation fix in 5.2.0 backported also in PHP 4 tree (in 4.4.5 maybe?)
Theoretically speaking (havent checked the default funcs internal cha
Hello,
On 1/15/07, Sara Golemon <[EMAIL PROTECTED]> wrote:
> As I told you, there was already a consensus on this solution, check
> my initial proposal (solution #2):
>
> http://news.php.net/php.internals/26965
>
No, that's a consensus on compile-time versus runtime. What I offered
in my post
I like Option 4.
-Andrei
On Jan 14, 2007, at 8:24 PM, Sara Golemon wrote:
Option 4:
Include fetchtype and subelement during runtime JIT callback
allowing JIT callback to only do work necessary to prepare for the
read/write call being performed.
e.g.
int php_example_jit_callback(int str_
As I told you, there was already a consensus on this solution, check
my initial proposal (solution #2):
http://news.php.net/php.internals/26965
No, that's a consensus on compile-time versus runtime. What I offered
in my post was four variants of how runtime could be implemented.
In respons
On 01/15/2007 12:14 PM, BuildSmart wrote:
Examine:
http://www.daleenterprise.com:8081/info.php
Look at 'Registered PHP Streams', 'Registered Stream Socket
Transports' and 'Registered Stream Filters'
This should be fixed in CVS.
--
Wbr,
Antony Dovgal
--
PHP Internals - PHP Runtime Develop
Hello Sara,
On 1/15/07, Sara Golemon <[EMAIL PROTECTED]> wrote:
For reasons best left on IRC, it looks like I'll be working on runtime
JIT. To that end, I've come up with a few proposals of varying
complexity and feature-set completeness:
Option 1:
Dump support for compile-time JIT and replace
On 01/15/2007 12:14 PM, BuildSmart wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
There seems to be a lot of issues in the build process on Mac OS X,
not to mention once you get them squared away the build still doesn't
work without editing the makefile and adding '-framework
Applica
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
There seems to be a lot of issues in the build process on Mac OS X,
not to mention once you get them squared away the build still doesn't
work without editing the makefile and adding '-framework
ApplicationServices'
Trying to build on Mac OS X
PHP 4 Bug Database summary - http://bugs.php.net
Num Status Summary (624 total including feature requests)
===[Apache2 related]==
38670 Open Whole 4.4.x branch has problem with open_basedir option nested
from Apache2
38915 Open
28 matches
Mail list logo
