Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:39116
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.198.237 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
         :content-type:references;
        b=FCrXJExm5JjHRFhfsj75s9+b4tYs+uFQxA51HQjpwzlvP5MrwtZgwQV79xdqz93Tf+
         Pp04yrK7PeddbfpKe2JjvYZC33ly/dDs2aQJv50IzNS57KqRGUJqKPpTmesJo8rfa4DG
         UC5tAQ5FXR5w/x21cdQ6h1SCnUM7k2jwDS7EA=
Message-ID: <7dd2dc0b0807201319m46f57595t13d5a44b1e12b579@mail.gmail.com>
Date: Sun, 20 Jul 2008 14:19:26 -0600
To: "Lukas Kahwe Smith" <mls@pooteeweet.org>
Cc: "Lars Strojny" <lstrojny@php.net>, internals@lists.php.net
In-Reply-To: <614DCEAD-CBB3-4D91-BFCF-CDC963D1C89E@pooteeweet.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_45663_11847849.1216585171743"
References: <1216464955.1815.0.camel@localhost>
	 <7dd2dc0b0807192245u2ec0ef7fw469b21ae3fc4f2f2@mail.gmail.com>
	 <614DCEAD-CBB3-4D91-BFCF-CDC963D1C89E@pooteeweet.org>
Subject: Re: [PHP-DEV] [RFC] E_USER_DEPRECATED
From: quickshiftin@gmail.com ("Nathan Nobbe")

------=_Part_45663_11847849.1216585171743
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On Sun, Jul 20, 2008 at 2:02 PM, Lukas Kahwe Smith <mls@pooteeweet.org>
wrote:

>
> On 20.07.2008, at 07:45, Nathan Nobbe wrote:
>
>  On Sat, Jul 19, 2008 at 4:55 AM, Lars Strojny <lstrojny@php.net> wrote:
>>
>>  Hi everbody,
>>>
>>> regarding my mail from yesterday, I've also created an RFC for the new
>>> error level.
>>>
>>> http://wiki.php.net/rfc/e-user-deprecated-warning
>>>
>>
>>
>> i definitely like the E_USER_DEPRECATED :D  im curious though, about
>> E_DEPRECATED.  is this for deprecated functions at the C level, or just
>> the
>> php api?  the reason i ask is because deprecation notices are already
>> issued
>> via the E_STRICT level, for example, when using is_a() today, w/ E_STRICT
>> enabled, the following is generated
>>
>> Strict standards: is_a(): Deprecated. Please use the instanceof operator
>> in
>> ...
>>
>> would, perhaps, the deprecation level for is_a() move to E_DEPRECATED (i
>> noticed its still there in 5.3)?
>>
>
>
> deprecation of is_a() was a mistake that has been reverted.


thats interesting, may i ask when that would be a better choice that
instanceof ?

and anyway, there are other examples as well, for example mktime(),

PHP Strict standards:  mktime(): You should be using the time() function
instead in ...

would this be another candidate to port to E_DEPRECATED ?  so i imagine
there will be some work to convert those E_STRICT errors regarding
deprecation to the new E_DEPRECATED level.  maybe that should go along w/
the patch.  as a matter of consistency, i think it would be best to move all
E_STRICT errors regarding deprecation to E_DEPRECATED in a single patch,
rather than a piecemeal fashion.

-nathan

------=_Part_45663_11847849.1216585171743--