Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:10763
Return-Path: <pollita@php.net>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 95447 invoked by uid 1010); 24 Jun 2004 16:30:08 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 95413 invoked by uid 1007); 24 Jun 2004 16:30:08 -0000
Message-ID: <20040624163007.95412.qmail@pb1.pair.com>
To: internals@lists.php.net
References: <20040622164209.23239.qmail@pb1.pair.com> <5.1.0.14.2.20040622180046.02e53768@127.0.0.1> <20040622171622.64014.qmail@pb1.pair.com> <5.1.0.14.2.20040624094922.02044458@127.0.0.1>
Date: Thu, 24 Jun 2004 09:29:54 -0700
Lines: 14
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Posted-By: 64.142.6.231
Subject: Re: [PHP-DEV] Bug 28879: Populating arrays with resources and   objects as offsets
From: pollita@php.net ("Sara Golemon")

> Maybe we should move this to an E_STRICT? E_WARNING is more consistent
with
> existing warnings but I wouldn't want to be over strict, especially when
> making this change a couple of weeks before release.
> We could escalate the warning for 5.1 if we feel we need to do so.
>
While I have a....layer of skepticism about the approach Aidan described, I
can see the wisdom in easing into error throwing.  Let's go ahed and start
with E_STRICT and discuss an elevation to either E_NOTICE (similar to
implicitly casting unknown constants to strings), or E_WARNING.

-Sara