Re: [PHP4BETA] cvs: php4 / NEWS TODO php4dllts.dsp php4ts.dsp /ext/mysql/libmysql/ libmysql.dsp /ext/standard/ array.c basic_functions.c
/sapi/apache/ php4apache.dsp /sapi/isapi/ php4isapi.dsp /sapi/nsapi/ php4nsapi.dsp
| From: | Chuck Hagenbuch | Date: | Sat, 03 Jun 2000 14:43:49 +0000 |
| Subject: | Re: [PHP4BETA] cvs: php4 / NEWS TODO php4dllts.dsp php4ts.dsp /ext/mysql/libmysql/ libmysql.dsp /ext/standard/ array.c basic_functions.c /sapi/apache/ php4apache.dsp /sapi/isapi/ php4isapi.dsp /sapi/nsapi/ php4nsapi.dsp |
||
| References: | 1 2 3 4 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-20118@lists.php.net to get a copy of this message | ||
Quoting Andi Gutmans <andi@zend.com>:
> I think what we should probably do is make the arrays format:
> array("classname", "methodname"); and not by object (or both)
How would that handle instances, though? Part of the point of being able to
use an object is that the object can contain additional state in a nice
package. That's hard to do with static classes (especially since we don't
have static variables in classes - although you can do interesting things
with functions that contain static variables).
If it's one or the other, I'm not sure which I'd pick - but it'd be nice to
have both.
-chuck
--
Charles Hagenbuch, <chagenbu@wso.williams.edu>
--
To understand recursion, one must first understand recursion.