Re: cvs: phpdoc /en/reference/bcompiler/functions bcompiler-write-header.xml /en/reference/calendar/functions cal-info.xml
/en/reference/fbsql/functions fbsql-create-db.xml fbsql-query.xml fbsql-start-db.xml /en/reference/filesystem/functions
| From: | Gabor Hojtsy | Date: | Fri, 12 Nov 2004 10:58:20 +0000 |
| Subject: | Re: cvs: phpdoc /en/reference/bcompiler/functions bcompiler-write-header.xml /en/reference/calendar/functions cal-info.xml /en/reference/fbsql/functions fbsql-create-db.xml fbsql-query.xml fbsql-start-db.xml /en/reference/filesystem/functions |
||
| References: | 1 2 3 4 5 | Groups: | php.doc |
| Request: | Send a blank email to phpdoc+get-969365037@lists.php.net to get a copy of this message | ||
Jakub, you are right. GobaWell, it is hard to decide now that PHP 5 has type hinting, which means that these class names actually become types. It is probably fine now to treat them as types, and use their names instead of the generic "object".OK. I will change all <type>object</type> different from stdClass to appropriate objects. Wouldn't it be confusing in some cases? E.g.: tidy tidy::__construct(...) Hope not. Other possibilities like "tidy object tidy::__construct()" or "object tidy tidy::__construct()" are even more confusing IMHO and different from type hinting syntax furthermore...