Not to throw a wrench in the wheel, but properties seem to be the more
appropriate pattern. Especially when taking PHP's object overloading
abilities into play. Accessors are a Java paradigm that's as half-baked
as it is repetitive, when you have overloading you no longer need
property accessors.
I vote (not to annoy george or anything, I'll write the code myself)
that we use properties and overloading. It will make it much easier to
instrospect the object with var_dump() and print_r(), and its the
cleaner implementation....
-Sterling
On Tue, 2003-07-01 at 09:34, Andrei Zmievski wrote:
> On Tue, 01 Jul 2003, Alan Knowles wrote:
> > It would be alot nicer if you could provide the majority of these as
> > object variables (and/or) functions, it would enable
> > print_r(new PHP_Function('counter'));
> > which would save a lot of messing around, and writing code for general
> > queries..
>
> I posed this question on the list when I was designing the API and
> majority agreed that methods were preferred over properties.
>
> -Andrei
> * Non-volatile, random-access, analog memory store... a book. *
--
"Whether you think you can or think you can't -- you are right."
- Henry Ford
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
