Re: [PHP-DEV] Access by siblings of (abstract) protected methods

Hi! > In summary: should abstract protected constructors be inaccessible by > siblings, as is true of __clone and __destruct? Should __construct, __clone > and __destruct always be accessible in relatives, as is true of other > methods? Depending on the answers, there could be a documentation issu

Re: [PHP-DEV] Access by siblings of (abstract) protected methods

Hi! > In summary: should abstract protected constructors be inaccessible by > siblings, as is true of __clone and __destruct? Should __construct, __clone > and __destruct always be accessible in relatives, as is true of other > methods? Depending on the answers, there could be a documentation issu

Re: [PHP-DEV] Access by siblings of (abstract) protected methods

Hi! > handler, which is why it behaves differently from normal methods. In the > time that I looked, I couldn't find where the access behavior for > __construct and __destruct was controlled in the source code. Access for functions is defined by zend_check_protected() and in zend_std_get_method()

[PHP-DEV] Access by siblings of (abstract) protected methods

Last month, Ahmad Farouk asked a question on StackOverflow about siblings accessing protected methods ( http://stackoverflow.com/q/9425770/90527) in PHP (I've been using 5.3.8 on OS X; others haven't mentioned which versions they've tested). He was surpris