Re: get_properties VS ce.default_properties
| From: | Piotr Pokora | Date: | Mon, 19 Feb 2007 13:26:02 +0000 |
| Subject: | Re: get_properties VS ce.default_properties | ||
| References: | 1 2 | Groups: | php.pecl.dev |
| Request: | Send a blank email to pecl-dev+get-4566@lists.php.net to get a copy of this message | ||
Pierre <pierre.php@gmail.com> wrote:
> What do you do in the derived class constructor? (sample script). It
> may help to reproduce the segfault.
Nothing. And I think it doesn't matter.
Sample script can be :
class MySuperClass extends Swish {
var $prop;
function __construct() {}
}
$obj = new MySuperClass();
echo $obj->prop;
print_r($obj);
Constructor will work , latter two cases will trigger segfault due to underlying data
not being explicitly set to NULL or whatever.
Look at swish constructor:
h = (struct php_sw_handle*)zend_object_store_get_object(object TSRMLS_CC);
h->h = SwishInit(indices);
My constructor makes this not being executed , right?
And in my code I do something similiar.
Is there any way to use such part of code if constructor is overwritten?
Later , is you for example invoke Swish::query you need to make this under the hood:
h = (struct php_sw_handle*)zend_object_store_get_object(getThis() TSRMLS_CC);
results = SwishQuery(h->h, query);
h->h is not a pointer to any data, not even NULL.
> > backtrace is useless here:
>
> debug mode?
PHP debug? I use PHP5 from binary packages :(
Piotras