Re: [RFC] [VOTE] __debugInfo()
| From: | Crypto Compress | Date: | Wed, 12 Feb 2014 20:40:45 +0000 |
| Subject: | Re: [RFC] [VOTE] __debugInfo() | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-72524@lists.php.net to get a copy of this message | ||
Hi,
so there maybe output not present in the object at all. Great source of confusion.
Solutions to problems created by RFCs are inherent and should not be solved in followup RFCs.
The __debugInfo RFC replaces one problem [1] by a subtile other one [2].
Why is it impossible to solve [1] and consequent [2] *within* this RFC?
[1] way too big object dumps
[2] no reliable way to create object dumps at all
Thank you!
cryptocompress