[PHP-DEV] CVS Account Request: raven

Translating the documentation into german language

--

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

[PHP-DEV] fix HEAD zend_hash_apply_with_argument

Hello,

Can someone apply this little patch to HEAD (Zend/zend_hash.c)?

These two lines have been removed by mistake in the last commit.

simple test (props access or any hash table usage):
<?php
class my {
  private $test=0;
  public $testp = 1;
  private $testarray = array();
}
$a = new my;
var_dump($a);

--Pierre

Index: zend_hash.c
===================================================================
RCS file: /repository/ZendEngine2/zend_hash.c,v
retrieving revision 1.142
diff -u -u -p -r1.142 zend_hash.c
--- zend_hash.c	31 Oct 2006 22:05:56 -0000	1.142
+++ zend_hash.c	1 Nov 2006 19:37:15 -0000
 <at>  <at>  -945,6 +945,8  <at>  <at>  ZEND_API void zend_hash_apply_with_argum
 		va_start(args, num_args);
 		hash_key.nKeyLength = p->nKeyLength;
 		hash_key.h = p->h;

[PHP-DEV] CVS Account Request: xmik

Hi,
 From few weeks i working in Polish translation team. I wanna be able to 
commit translation changes direct to main cvs, beacouse our acccess to 
team cvs not always working from some reasons. I'll be very happy if You 
give me a chanse to join to php coummunity and help peoples involved in 
a project (not only in translation aspect).

--

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

[PHP-DEV] CVS Account Request: lucraymond

submitting packages

--

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

[PHP-DEV] 5.2 Win32 last build on Oct 31, 2006 07:30 GMT

Hi.

Just a heads up on the Win32 builds. Nothing since early October 31st.

-- 
-----
Richard Quadling
Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731
"Standing on the shoulders of some very clever giants!"

--

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

[PHP-DEV] ReflectionProperty change between 5.1 and 5.2

Hi,

Lets say I have a class

class MyClass
  protected $foo = 'bar';
}

In PHP 5.1 I could do

$myobj = new MyClass();
$c = new ReflectionClass($myobj);
$p = $c->getProperty('foo');
echo $p->getValue($myobj); // bar

But in PHP 5.2 I now get an exception with "Cannot access non-public member 
MyClass::foo"

Yes, I do know that "protected" is supposed to make the variable internal 
(hence non-public), but shouldn't the ReflectionAPI enable one to "reverse 
engineer" all classes and properties - including the ones hidden in run-time? 
And if not, then how come it was like this in 5.1?

-fangel

--

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

[PHP-DEV] [PATCH] don't override error_reporting() in module dom

Hi,
this patch removes the prevaricative code in ext/dom/document.c that 
forcibly
reports errors in xml data overriding the error_reporting value set by 
the user.

If the user intentionally sets $dom->recover to true and disables E_WARNING
he obviously wants php to shut up in all cases, even when the xml fed to 
dom is broken;
php should obediently comply, not take initiatives on its own accord.

Please, consider this patch for inclusion in HEAD.

    Nico

--

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] What version introduced RTLD_DEEPBIND?

On Fri, Oct 27, 2006 at 12:12:46PM -0400, Brian J. France wrote:
> and I plan on removing it from our internal builds as it causes more  
> problems than I think it fixes (on RHEL only).

Hi, what problems do you see from the use of RTLD_DEEPBIND?

Regards,

joe

--

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] What version introduced RTLD_DEEPBIND?

On Nov 3, 2006, at 8:20 AM, Joe Orton wrote:
> On Fri, Oct 27, 2006 at 12:12:46PM -0400, Brian J. France wrote:
>> and I plan on removing it from our internal builds as it causes more
>> problems than I think it fixes (on RHEL only).
>
> Hi, what problems do you see from the use of RTLD_DEEPBIND?

Where to start? :)

First issue we have is we build our extension linked with a static  
library called apstubs.  apstubs is a hack where all exported apache  
functions, structs, etc are defined weak (function print a error and  
abort).  We do this so PHP extensions that are mainly for apache  
only, can still load on the command line without issue (assuming weak  
code path is not executed).  When things are run in apache the strong  
symbols from apache override the weak ones in the library.

With RTLD_DEEPBIND we don't get this behavior because that flag and  
force it to use the weak symbols even when the strong symbols are  
present.  I understand the reasoning for this behavior (not being  
able to namesapce and having duplicate symbols), but we rely on weak/ 
strong symbols in a lot of our code and this just causes more problems.

A second issue we have is when RTLD_DEEPBIND is defined the rtld  
can't find symbols in a already loaded lib.  This one is strange and  
I can't figure it out, but if I had to guess I would be it is a  
problem with libraries not getting unloaded between the first and  
second pass of apache startup (which we are trying to track down now,  
expect a new or updated RH bug soon if we find something).  But for  
some reason turning off RTLD_DEEPBIND fixes the core dump (not the  

Re: [PHP-DEV] Why 5.2 should not be delayed for E_DEPRECATED

Ilia Alshanetsky wrote:
> Thanks to Hannes we have a fairly complete list of changes in the error
> conditions, so far people who have commented out it did not appear to
> have identified anything objectionable. We need to make a decision on
> how to proceed, either to roll 5.2.0 now or wait another week. My vote
> is to roll things now...

Out of curiosity What's the plan for E_DEPRECATED now?

Regarding the release of PHP 5.2 and OO strictness:
I never got any comment about my OO strictness patch to not complain
about adding default values to parameters or changes on static methods
which both do not break the quoted
http://en.wikipedia.org/wiki/Liskov_substitution_principle

I would have hoped for a little info why this patch was not considered.

Regards,
- Chris

--

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php