Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:83043 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 78194 invoked from network); 18 Feb 2015 11:13:32 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Feb 2015 11:13:32 -0000 Authentication-Results: pb1.pair.com header.from=francois@php.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=francois@php.net; spf=unknown; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 212.27.42.2 as permitted sender) X-PHP-List-Original-Sender: francois@php.net X-Host-Fingerprint: 212.27.42.2 smtp2-g21.free.fr Received: from [212.27.42.2] ([212.27.42.2:50214] helo=smtp2-g21.free.fr) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 1C/A9-18888-AD374E45 for ; Wed, 18 Feb 2015 06:13:31 -0500 Received: from moorea (unknown [82.240.16.115]) by smtp2-g21.free.fr (Postfix) with ESMTP id F135A4B0194; Wed, 18 Feb 2015 12:13:08 +0100 (CET) Reply-To: To: "'Tim Bezhashvyly'" , "'PHP Internals'" References: <3FCFEC72-64AD-42E3-8512-E3DACDE6FBD7@gmail.com> <052A15EB-E546-4FE3-9316-506931574948@gmail.com> In-Reply-To: <052A15EB-E546-4FE3-9316-506931574948@gmail.com> Date: Wed, 18 Feb 2015 12:13:25 +0100 Message-ID: <02fa01d04b6b$ea7feae0$bf7fc0a0$@php.net> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQGdX4xI4Vkvj7yxG/xqkDs+ng/OYQJu5iVWArO2+0mdMwIFAA== Content-Language: fr X-Antivirus: avast! (VPS 150217-2, 17/02/2015), Outbound message X-Antivirus-Status: Clean Subject: RE: [PHP-DEV] RFC Proposal From: francois@php.net (=?utf-8?Q?Fran=C3=A7ois_Laupretre?=) Hi Tim, As I already told you, you should proceed step by step. Implementing = immutable properties *and* removing constants is just a too big step. = And, IMO, one may pass, while the second one has no chance, especially = if you propose to remove PHP constants as well as class constants, = without a BC layer. Unfortunately, while we can sometimes break BC, we = are not designing from scratch. Now, if you want to link both features and withdraw the whole, that's = your choice, and none will blame you for that. You were asking for = opinions that's only mine. Regards Fran=C3=A7ois > -----Message d'origine----- > De : Tim Bezhashvyly [mailto:tim.bezhashvyly@gmail.com] > Envoy=C3=A9 : mercredi 18 f=C3=A9vrier 2015 10:44 > =C3=80 : PHP Internals > Objet : Re: [PHP-DEV] RFC Proposal >=20 > Dear internals, >=20 > my RFC was not about dropping just class constants but constants in = general. > Now I realise that you are not ready for this and most likely will = never be. > Thus I=E2=80=99m withdrawing my proposal. >=20 > Regards, > Tim >=20 > > On 18 Feb 2015, at 06:59, Dmitry Stogov wrote: > > > > > > > > On Tue, Feb 17, 2015 at 8:35 PM, Tim Bezhashvyly > > wrote: > > Dear PHP internals, > > > > this is my first RFC proposal and I am not sure if in this email is = supposed to > contain all RFC details or just a brief idea .. which is to drop PHP = constants in > favour of =E2=80=9Cfinal" immutable variables. > > > > I think dropping constant or class constants is a bad idea. > > Adding immutable variables may make sense, but you should explain = use- > cases, behavior, syntax, implementation details, etc > > > > Thanks. Dmitry. > > > > > > This is basically only a concept but I can also handle its = implementation. > > > > Please let me know if I have to provide any additional details. > > > > Regards, > > Tim > > -- > > PHP Internals - PHP Runtime Development Mailing List > > To unsubscribe, visit: http://www.php.net/unsub.php > > > > >