Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:18668
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <009901c5b165$3df9ee10$6c051fac@lighthammer>
To: <internals@lists.php.net>
References: <431ACE6C.3060006@php.net> <73.1B.33268.806DA134@pb1.pair.com>
Date: Sun, 4 Sep 2005 08:27:43 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
Subject: Re: E_NOTICE/E_STRICT/E_WARNING thrown on bad arrays initialization?
From: pollita@php.net ("Sara Golemon")

>> As you surely know, arrays are often badly initialized:
>>
>> <?php
>> // $array is undefined
>> $array['index'] = 'value';
>>  ?>
>>
>> Wouldn't it be such a good thing to let the programmers know that this
>> is a bad habit, by throwing a +/- pedantic error ? I'm not sure which
>> type would suit for it, but I think its important enough to throw a
>> E_NOTICE.
>>
>I agree. I've always found it weird that no notice is thrown in this
> situation. Still I discourage people to code like this.
> 
This was brought up about a year ago and dismissed.

-Sara