Re: [PHP4BETA] OOP issue
| From: | Kristian Koehntopp | Date: | Tue, 16 Nov 1999 18:33:09 +0000 |
| Subject: | Re: [PHP4BETA] OOP issue | ||
| References: | 1 2 | Groups: | php.version4 |
| Request: | Send a blank email to php-version4+get-6304@lists.php.net to get a copy of this message | ||
Andi Gutmans wrote:
> Why? In any case you have to hardcode X in the extends line so how does it
> make it any more hardcoded if you also need to hardcode the X::X in the
> constructor?
I do normalize my data models, because I do not want to keep and
update data in more than one place. Not normalizing does lead to
all kinds of anomalies and errors. In all other places I
reference the one and single original data value.
Similarly, I don't think that keeping the name of the superclass
in more than one place in my code is a good idea, because if
that name changes, I'll have to change it all over the place. So
I think it is enough to mention the name of the superclass in
"extends ..." one time and the language should reference this
automatically within the class. Anyway, I'd like a
$super::_init() or $super->_init() (the second version looks
more natural to me because of $this->_init()) much better than
X::x().
Kristian
--
Kristian Köhntopp, NetUSE Kommunikationstechnologie GmbH
Siemenswall, D-24107 Kiel, Germany, +49 431 386 436 00
Using PHP3? See our web development library at
http://phplib.netuse.de/ (We have moved! Update your
bookmarks!)