Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:19757
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Thu, 27 Oct 2005 13:10:20 +0300 (EEST)
Reply-To: Jani Taskinen <sniper@iki.fi>
To: Ilia Alshanetsky <ilia@prohost.org>
cc: internals@lists.php.net
In-Reply-To: <435FF414.3000303@prohost.org>
Message-ID: <Pine.LNX.4.61.0510271308210.15009@arfg.argcubovn.sv>
References: <4e36d31d0510261018t639c472x9efaaf7af61a9ddb@mail.gmail.com>
	<Pine.LNX.4.61.0510262230020.11940@arfg.argcubovn.sv> <435FDC41.30207@php.net>
	<435FF414.3000303@prohost.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Subject: Re: [PHP-DEV] Re: foreach with null
From: sniper@iki.fi (Jani Taskinen)

On Wed, 26 Oct 2005, Ilia Alshanetsky wrote:

>
> Greg Beaver wrote:
>> amen, this behavior makes no sense even though sizeof() is an alias to
>> count().  sizeof('this') and sizeof('this long thing') are both 1, which
>> makes no sense.  I would go so far as to say a E_NOTICE is more
>> appropriate than E_STRICT - you should only be using count() for
>> arrays/objects.
>
> Actually this result makes perfect sense since type conversion changes
> string into array('your string') and does a count of that, which is 1.

     This is yet another magic type casting I'd like to get rid of..
     Strict is not always bad, mmkay? :)

     I got bitten by this (unexpected?) behaviour of count() myself this week.
     I must have been strict in my mind and not passed anything but arrays
     to it before this. :)

     --Jani