Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:49499
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.211.66 cause and error)
To: Adam Harvey <aharvey@php.net>
Cc: PHP internals <internals@lists.php.net>
In-Reply-To: <AANLkTikP0cooG91ZgSeRS+H0fXCjDdLRUpO53OhT8FYC@mail.gmail.com>
References: <AANLkTikP0cooG91ZgSeRS+H0fXCjDdLRUpO53OhT8FYC@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Date: Tue, 24 Aug 2010 20:27:43 +0200
Message-ID: <1282674464.3333.119.camel@guybrush>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [PATCH] #52563: Adding E_NONE and/or E_EVERYTHING
 constants
From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

On Tue, 2010-08-24 at 18:49 +0800, Adam Harvey wrote:
> Johannes has pointed out on IRC that E_NONE does already exist in some
> projects, so that's an argument against it.

Yeah, I did a quick code search, which gave some results defining a
constant with that name. This means adding this in 5.3 would be a
annoyance and upgrading from X.Y.(Z-1) to X.Y.Z should be a no
brainer ... on the other hand the fact that people are defining such a
constant and the bug report show that there is some need.

I myself don't see a point in a constant for an empty bit mask. As an
empty bit mask means 0 ... on the other hand it doesn't cost us much.

So, I'm +/- 0 on this for trunk.

johannes