Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:21832
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
To: "Ian P. Christian" <pookey@pookey.co.uk>
Cc: internals@lists.php.net, Sean Coates <sean@caedmon.net>
In-Reply-To: <200602092210.06390.pookey@pookey.co.uk>
References: <200602092154.01908.pookey@pookey.co.uk>
	<43EBBD74.8010703@caedmon.net>  <200602092210.06390.pookey@pookey.co.uk>
Content-Type: text/plain
Organization: InterJinn
Message-ID: <1139524120.2072.42.camel@blobule.suds>
Mime-Version: 1.0
Date: Thu, 09 Feb 2006 17:28:40 -0500
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] 'odd' handling of $moo['bar'] where $moo is a string
From: robert@interjinn.com (Robert Cummings)

On Thu, 2006-02-09 at 17:10, Ian P. Christian wrote:
> On Thursday 09 February 2006 22:08, Sean Coates wrote:
> > It's cast to an integer.
> 
> Ahh.. I see. That does make sense now as to why it results in the first char 
> in the array - however I still think it makes more sense not to cast, but 
> rather to give a fatal error.

PHP is primarily a web language. Many indexes are pulled from $_GET and
$_POST and for obvious reasons are strings. One of the convenience
factors of PHP is that noobs don't need to think about casting their
strings to ints to index.

Cheers,
Rob.
-- 
.------------------------------------------------------------.
| InterJinn Application Framework - http://www.interjinn.com |
:------------------------------------------------------------:
| An application and templating framework for PHP. Boasting  |
| a powerful, scalable system for accessing system services  |
| such as forms, properties, sessions, and caches. InterJinn |
| also provides an extremely flexible architecture for       |
| creating re-usable components quickly and easily.          |
`------------------------------------------------------------'