Re: [ZEND-ENGINE-CVS] cvs: ZendEngine2(PHP_5_1) /zend_compile.c
| From: | Antony Dovgal | Date: | Sat, 19 Nov 2005 11:26:27 +0000 |
| Subject: | Re: [ZEND-ENGINE-CVS] cvs: ZendEngine2(PHP_5_1) /zend_compile.c | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.zend-engine.cvs |
| Request: | Send a blank email to php-zend-engine-cvs+get-4376@lists.php.net to get a copy of this message | ||
On 19.11.2005 14:20, Stanislav Malyshev wrote:
AD>>I think yes, NULL should be able to represent "nothing of any type". AD>>That makes it consistent and that's what I would expect. Would you expect to get a warning when you pass variable that is typehinted as array to, for example, join()? Would you expect a warning if you pass null there?No, I wouldn't expect to get a warning from a function which uses array() for typehinting. NULL is just "nothing", if a function were expecting an array and got nothing - fine, we got nothing as the result either. -- Wbr, Antony Dovgal