Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:64436
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.219.53 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <8D.41.07178.7380BD05@pb1.pair.com>
References: <8D.41.07178.7380BD05@pb1.pair.com>
Date: Wed, 26 Dec 2012 16:28:48 +0200
Message-ID: <CANVTSm4KiD8uY_aXLhSzhC9ER947PdHjtjGSjaGHvxqH9S3i_g@mail.gmail.com>
To: Yussuf Khalil <dev@pp3345.de>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=bcaec54ee86cd84c1904d1c24048
Subject: Re: [PHP-DEV] RFC: Add a deprecated modifier for functions
From: g.b.yahav@gmail.com (Yahav Gindi Bar)

--bcaec54ee86cd84c1904d1c24048
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Dec 26, 2012 at 4:22 PM, Yussuf Khalil <dev@pp3345.de> wrote:

> Hello,
>
> I have created an RFC about adding a deprecated modifier for functions in
> PHP, see https://wiki.php.net/rfc/**deprecated-modifier<https://wiki.php.net/rfc/deprecated-modifier>.
> What are your thoughts on this?
>
> Thank you,
> Yussuf Khalil
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
Hi!
I think the idea of marking functions as deprecated is great and the
current way of throwing E_DEPRECATED error by trigger_error can be
improved. In the current state.

That's being said, I don't think that adding a deprecated keyword is the
solution, since now we can write documentation and set a "@deprecated" mark.
I think, that the best solution is the attributes concept that was rejected
before and should be re-considered after the last releases changes and
language improvements.
A few built in attributes, such as <Deprecated> can be great.

What do you think?

--bcaec54ee86cd84c1904d1c24048--