Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:19150
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <43357E36.4060706@nohn.net>
Date: Sat, 24 Sep 2005 18:26:30 +0200
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
MIME-Version: 1.0
To: Sara Golemon <pollita@php.net>
Cc: internals@lists.php.net
References: <431ACE6C.3060006@php.net> <73.1B.33268.806DA134@pb1.pair.com> <009901c5b165$3df9ee10$6c051fac@lighthammer>
In-Reply-To: <009901c5b165$3df9ee10$6c051fac@lighthammer>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: E_NOTICE/E_STRICT/E_WARNING thrown on bad arrays
	initialization?
From: sebastian@nohn.net (Sebastian Nohn)

Sara Golemon wrote:
>>> 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.

No reason to not bring it up again.

Sebastian