It is/was attached to the mail I sent out; maybe gmail isn't so smart
with text attachments.
I've attached it to this mail, so you should get it this time.
--Wez.
On Sun, 06 Mar 2005 08:41:53 +0200, Zeev Suraski <[EMAIL PROTECTED]> wrote:
> At 08:18 06/03/2005, Wez Furlong wrote:
> >Any objecti
Wez Furlong wrote:
Hi Wez,
The diff is not attached. I think the mailling lists strip attachments?
Regards
--jm
It is/was attached to the mail I sent out; maybe gmail isn't so smart
with text attachments.
I've attached it to this mail, so you should get it this time.
--Wez.
On Sun, 06 Mar 2005 08:
Jacques Marneweck wrote:
I think the mailling lists strip attachments?
Attaching a file to this message to test the theory.
For the list of people who've put work into PHP, please see
http://www.php.net/credits.php
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: htt
Hello,
I saw there are two new ReflectionClass methods:
* getStaticPropertyValue()
* getStaticPropertyValue()
How do these differ (excepting being one method call) from:
$value= $reflectionClass->getProperty('instance')->getValue();
and
$reflectionClass->getProperty('instance')->setVal
I think for me, it is the most comfortable way to refelect the properties.
When it is refelecting
it should follow a std. pattern
- Original Message -
From: "Timm Friebe" <[EMAIL PROTECTED]>
To: "internals"
Sent: Sunday, March 06, 2005 5:11 PM
Subject: [PHP-DEV] (s|g)etStaticPropertyValu
Hi,
the following script:
getProperty('instance')->getValue());
?>
prints "UNKNOWN:0" - expected behaviour would be to print "NULL".
Attached is a diff against zend_reflection_api.c which fixes this.
--
Timm
If it ain't broken, it doesn't have enough features yet
Index: Zend/zend_reflection_ap
At 13:26 06/03/2005, Timm Friebe wrote:
Hello,
I saw there are two new ReflectionClass methods:
* getStaticPropertyValue()
* getStaticPropertyValue()
How do these differ (excepting being one method call) from:
$value= $reflectionClass->getProperty('instance')->getValue();
and
$reflectionCla
On Sun, 6 Mar 2005, Zeev Suraski wrote:
> At 06:47 06/03/2005, Yermo Lamers wrote:
>
> >What is the proper way to return a NULL condition from a method that
> >returns a reference?
> >
> >function &testfunc()
> >{
> >return NULL;
> >}
> >
> >generates:
> >
> >"Strict Standards: Only variable refer
Hey,
Someone I know is looking for an experienced web graphics designer
(including HTML editing) who will do some occasional work for a (very)
large company.
If you know anyone please let me know directly. It's quite urgent...
Sorry for spaming the list.
Thanks,
Andi
--
PHP Internals - PHP Runti
Hi,
We're getting quite a few reports of PEAR segfaulting on a
debug_backtrace() call found in the constructor of PEAR_Error. Jan
Schneider reported that it seemed to occur when one of the methods in
the trace happened in a file that the uid did not have write access to
(i.e. a PEAR file insta
On Sun, 6 Mar 2005, Greg Beaver wrote:
> We're getting quite a few reports of PEAR segfaulting on a
> debug_backtrace() call found in the constructor of PEAR_Error. Jan
> Schneider reported that it seemed to occur when one of the methods in
> the trace happened in a file that the uid did not have
>> >Is the correct approach to do something like:
>> >
>> >function &testfunc()
>> >{
>> >$nullVar = NULL;
>> >return $nullVar;
>> >}
>>
>> That'd work, yep.
>
> Wrong ;-) It causes problems with reference counting - and will segfault
> PHP after some time.
>
> Derick
Then what is the correct app
At 17:06 06/03/2005, Derick Rethans wrote:
On Sun, 6 Mar 2005, Zeev Suraski wrote:
> At 06:47 06/03/2005, Yermo Lamers wrote:
>
> >What is the proper way to return a NULL condition from a method that
> >returns a reference?
> >
> >function &testfunc()
> >{
> >return NULL;
> >}
> >
> >generates:
> >
>> > >function &testfunc()
>> > >{
>> > >$nullVar = NULL;
>> > >return $nullVar;
>> > >}
>> >
>> > That'd work, yep.
>>
>>Wrong ;-) It causes problems with reference counting - and will segfault
>>PHP after some time.
>
> Hmm, that in itself shouldn't cause any problems unless it's coupled with
>
The patch looks good. The only thing I'd add is getting rid of the code
that became redundant, for clarity (the switch() is not needed in
module_registry_cleanup(), and the switch() in
module_registry_unload_temp() can be an if()). Did you intend to also
commit it to the 5.0 branch or only 5.
I've been writing some extensions with great success however, I have
one that I'm working on (rewriting an existing extension that has never
functioned properly to the best of my knowledge) that is causing me
headaches.
This problem seems to occur regardless of the version of PHP being
utilize
I've been writing some extensions with great success however, I have
one that I'm working on (rewriting an existing extension that has never
functioned properly to the best of my knowledge) that is causing me
headaches.
This problem seems to occur regardless of the version of PHP being
utilize
17 matches
Mail list logo
