Re: Re: Design points (was: parent_ctor())
| From: | Stanislav Malyshev | Date: | Tue, 18 Jul 2000 16:13:50 +0000 |
| Subject: | Re: Re: Design points (was: parent_ctor()) | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-24974@lists.php.net to get a copy of this message | ||
KK>> Actually, I consider the ability to keep structures with references
KK>> across serialization essential (*1), and the language below should make
KK>> this easy, or at least possible.
But that doesn't mean PHP references don't work right. They aren't just a
tool for what you want to do (yet?)
KK>> (*1) As I explained, referenced are to data structures what foreign
KK>> keys are to sql tables. They are needed to normalize a design.
BTW, not that SQL tables _do not_ have any "references". In most
implementations, AFAIK, foreign keys work in entirely different way. In
SQL foreign key is a property of the table, not the row, AFAIK. So to make
1-1 correspondence between SQL foreign keys and PHP references is not
right.
--
Stanislav Malyshev stas@zend.com
+972-3-6139665