[TYPO3-dev] Extensions need update for 4.3!

Dmitry Dulepov dmitry at typo3.org
Thu Oct 9 16:03:55 CEST 2008


Hi!

Ernesto Baschny [cron IT] wrote:
> The API (meaning the "code") always allowed "NULL" values to be passed
> as parameters, that has not changed even with PHP5. There was no type
> hinting before (4.2 works fine in PHP5, not extension broke). We gain
> nothing in changing it now apart from the fact that some extensions will
> stop working. I don't see a reason to do that. We could stop people
> passing strings or integers, that is ok ("education"), my suggestion was
> exactly that: allow only arrays AND the NULL value (nothing else). Won't
> break any extension, we still have type hinting, everybody happy?
> 
> We need to use some common sense here and there in those kind of stuff.

I do not think it is named common sense :( It is stimulating bad coding style.

I think we should use Steffens suggestion instead ("array $param = array()").

We never declared we allow NULL.

-- 
Dmitry Dulepov
TYPO3 Core team
My TYPO3 book: http://www.packtpub.com/typo3-extension-development/book
In the blog: http://typo3bloke.net/post-details/duplicate_content_with_realurl/




More information about the TYPO3-dev mailing list