Re: [RFC] [VOTE] __debugInfo()
| From: | George Bond | Date: | Mon, 03 Feb 2014 21:35:03 +0000 |
| Subject: | Re: [RFC] [VOTE] __debugInfo() | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-72129@lists.php.net to get a copy of this message | ||
On 3 February 2014 21:11, Crypto Compress <cryptocompress@googlemail.com>wrote:
> Meant output of var_dump is unexpected.
But that's not a B/C *break*, because users are explicitly instructed not
to write functions beginning with double underscores unless they want magic
functionality, and since this is *new* magic functionality
*no*correctly-constructed code will contain a function named
"__debugInfo()".
Any old code which does contain such a function is already explicitly
standards-defying, and so does not deserve any B/C maintenance. That's
the whole point in reserving the whole namespace of
double-underscore-prefixed functions for future magic behaviour.
The fact that with this function developers can write
*new*weird/broken/counter-intuitive code like you write is certainly
valid. But
it's not a B/C issue.
--G