Re: svn: /php/php-src/trunk/ NEWS ext/json/json.c ext/json/php_json.h ext/json/tests/serialize.phpt
| From: | Stanislav Malyshev | Date: | Wed, 12 May 2010 02:25:08 +0000 |
| Subject: | Re: svn: /php/php-src/trunk/ NEWS ext/json/json.c ext/json/php_json.h ext/json/tests/serialize.phpt | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-48263@lists.php.net to get a copy of this message | ||
Hi!
Add JSON_Serializable interface Objects implementing JSON_Serializable will have their ->jsonSerialize() method called Similar to serialize() and __sleep()Why should we have special mechanism for JSON? I.e., now we have one for serialize(), separate one for json, then we'd have separate one for storing object as XML or YAML, etc. etc. IMHO it's not a very good design - having separate method for every format of data storage. Why can't we just use whatever serialize() would see and wrap it in JSON after that? -- Stanislav Malyshev, Zend Software Architect stas@zend.com http://www.zend.com/ (408)253-8829 MSN: stas@zend.com