Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:9719
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <5.1.0.14.0.20040507202204.028a1120@mail.ionzoft.com>
Date: Fri, 07 May 2004 20:25:54 -0400
To: internals@lists.php.net
In-Reply-To: <31151523.20040508004308@marcus-boerger.de>
References: <20040507210516.92262.qmail@pb1.pair.com>
 <20040507210516.92262.qmail@pb1.pair.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: Re: [PHP-DEV] Implicit Arrays and E_STRICT
From: jason@ionzoft.com (Jason Garber)

I would view implicit array creation as a slightly negative thing, similar 
to accessing the value of a variable that does not exist.

We run in E_ALL mode and write our code to avoid all E_NOTICEs.  For 
instance, before using an array, I always initialize it using $aItems = 
array();

I'm in favor of issuing an E_NOTICE in response to this.

~Jason

At 5/8/2004 12:43 AM +0200, Marcus Boerger wrote:
>Hello Sara,
>
>i like to see one of those too and i have no preference for one of them.
>
>marcus
>
>Friday, May 7, 2004, 11:05:15 PM, you wrote:
>
> > This topic got quietly dropped last week, but I'd like to make one last
> > plea.  I'd like to see Zend throw an E_STRICT when arrays are implicitly
> > created.  I know there were objections to E_NOTICE, but did anyone have
> > violent objections to E_STRICT?
>
> > -Sara
>
>
>
>
>--
>Best regards,
>  Marcus                            mailto:helly@php.net
>
>--
>PHP Internals - PHP Runtime Development Mailing List
>To unsubscribe, visit: http://www.php.net/unsub.php