Re: [PHP-DEV] [RFC][Discussion] Consistent callables

2017-09-04 Thread Stephen Reay
Sent from my iPhone > On 5 Sep 2017, at 03:05, Dan Ackroyd wrote: > > Stephen Reay wrote: >> Regarding the big change you suggest, making protected/private methods >> return false unless a new third parameter is true in is_callable(): >> I think you need to make your intention a *lot* clearer

Re: [PHP-DEV] [RFC][Discussion] Consistent callables

2017-09-04 Thread Dan Ackroyd
Stephen Reay wrote: > Regarding the big change you suggest, making protected/private methods return > false unless a new third parameter is true in is_callable(): > I think you need to make your intention a *lot* clearer On 29 May 2017 at 12:01, Rowan Collins wrote: > Regarding is_callable,

Re: [PHP-DEV] [RFC][Discussion] Consistent callables

2017-05-29 Thread Rowan Collins
On 28 May 2017 22:23:30 BST, Dan Ackroyd wrote: >Hi, > >I'd like to introduce an RFC to cleanup the behaviour of callables and >related functions in PHP. > >https://wiki.php.net/rfc/consistent_callables Hi Dan, I like the principle behind this RFC, so thanks for tackling it. A few comments came

Re: [PHP-DEV] [RFC][Discussion] Consistent callables

2017-05-29 Thread Andrey Andreev
Hi, On Mon, May 29, 2017 at 12:28 PM, Stephen Reay wrote: > > Regarding the big change you suggest, making protected/private methods return > false unless a new third parameter is true in is_callable(): > > I think you need to make your intention a *lot* clearer under the "Private > and protect

Re: [PHP-DEV] [RFC][Discussion] Consistent callables

2017-05-29 Thread Stephen Reay
> On 29 May 2017, at 04:23, Dan Ackroyd wrote: > > Hi, > > I'd like to introduce an RFC to cleanup the behaviour of callables and > related functions in PHP. > > https://wiki.php.net/rfc/consistent_callables > > Note, this RFC targets PHP 8, with soft deprecations in PHP 7.3 and > deprecation