Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:91921 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 59601 invoked from network); 24 Mar 2016 19:16:00 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Mar 2016 19:16:00 -0000 Authentication-Results: pb1.pair.com smtp.mail=mtkocak@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=mtkocak@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.53 as permitted sender) X-PHP-List-Original-Sender: mtkocak@gmail.com X-Host-Fingerprint: 74.125.82.53 mail-wm0-f53.google.com Received: from [74.125.82.53] ([74.125.82.53:35724] helo=mail-wm0-f53.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id BF/68-15440-FEC34F65 for ; Thu, 24 Mar 2016 14:16:00 -0500 Received: by mail-wm0-f53.google.com with SMTP id l68so249039080wml.0 for ; Thu, 24 Mar 2016 12:15:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=W7hs9xXicoeK1vdFVOzCSYXu8wSTpChQMXeuPwu7nGo=; b=YPsUT6J6Z21lpwM4goa0Lj7Zs7s1Xitp4KabgCkeR0dt0N9f3CxRQZge3AR2LW409x HGPTfzViOaBmDwLOtHf0MlX8TeDJZ0AWvZGSefwrwyQrRsE1OSdnJ1G87RD47AL+z3pZ CTT0sjVBIkDJ8XZpu7hYtUvhFsvrvqojBUM6gGLpjdAV8oZmdqT5o5FnMYvQa6KTuiSl j1ygscWCsNeFufH7t8WgkPULKrj/RaMlwffVgGYuLhg3/COt9JaTF/MAXGMsvWcpNUFC wLvIqr5IOgb21WyOA5Oo5k5+QQL5NPsDd9tfw0fVpFw4dKuZxNQk+2u53HQ+XUQLEup4 ZUPw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=W7hs9xXicoeK1vdFVOzCSYXu8wSTpChQMXeuPwu7nGo=; b=gUb2Ps+HgHBKEmi/wgquK309fZxJoC5V+uockaYcpiGA9wnlu/VoOSUMYhft1OAGLb LfByPYVW+AkLT6q0GzpxeXPOm06U9hm1zWICex+FsdHPjZt2/nGJT6K06LHuOIhsZB+y 1cIpKnm12pEWtA32SFkiDAI31zH2YQGTPkDoZW7ExzF+kjxI8tvZgCiQIYOVnAjvB+PH kZzTKxzg9K6LU3Bt7giDJFlJErEuzi9wWM9J7iL1xPUfmzYWIWGcWQdkgpqmKpI9Of+i IOZfWhEEi4+f/xe5xTtYArAFw36W8BsQhej5MlTf6CVkMZ34n14T+bqDr3xXghzz5IGX r0TQ== X-Gm-Message-State: AD7BkJKuwsIHwSBCS+hjVMIweliijS/Uwa9yGDQbn2yrd/e9Cf6We/06f4n85jTrPlt0HiIwT9Q46uQZhzaVvA== MIME-Version: 1.0 X-Received: by 10.194.2.169 with SMTP id 9mr11571368wjv.7.1458846956650; Thu, 24 Mar 2016 12:15:56 -0700 (PDT) Sender: mtkocak@gmail.com Received: by 10.194.17.169 with HTTP; Thu, 24 Mar 2016 12:15:56 -0700 (PDT) In-Reply-To: References: Date: Thu, 24 Mar 2016 20:15:56 +0100 X-Google-Sender-Auth: im7d82oXEXM8tS20uPifHf8Fgjs Message-ID: To: "Colin O'Dell" Cc: PHP Internals Content-Type: multipart/alternative; boundary=047d7b3a8170a20b55052ed04678 Subject: Re: [PHP-DEV] [VOTE] var deprecation From: mtkocak@mtkocak.net (Mutlu Kocak) --047d7b3a8170a20b55052ed04678 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable +1 var should be deprecated On Thursday, 24 March 2016, Colin O'Dell wrote: > There have been some last-minute concerns raised about var being reserved > "for future usage". My intent was that var couldn't be used for > function/class names IN CASE it was re-used in the future, but not > encouraging it to be re-used. I'd assume that reusing it would require a > separate RFC to pass by a 2/3rds margin. > > Does anyone disagree with this interpretation or feel that it should be > explicitly stated? Would anyone change their vote from NO to YES if "for > future usage" was removed (but "reserving it" was kept in)? Would anyone > change their vote from NO to YES if the question of "reserving it" could = be > voted on separately? > > If so, and we can stop the vote to make these changes, I'd strongly prefe= r > to do so. I'd hate for three words to sink the entire RFC. > > (My apologies if this belongs in the discussion thread instead) > > Regards, > > Colin > > On Thu, Mar 24, 2016 at 8:40 AM Colin O'Dell > wrote: > > > Hello everyone, > > > > It has been two weeks since discussion started on the RFC to deprecate > and > > eventually remove the "var" keyword (and one month since the idea was > > originally proposed). > > > > This RFC has therefore been moved to the "In Voting" state. Voting wil= l > > begin immediately and will end in one week. > > > > You can find the full RFC (including the proposed patch and automatic > > upgrade tool) here: https://wiki.php.net/rfc/var_deprecation > > > > I encourage everyone to read the RFC and cast your vote towards whichev= er > > option you feel is the best for the language and the community. > > > > Regards, > > > > Colin O'Dell > > > --=20 Mutlu Ko=C3=A7ak | Computer Scientist & Engineer Mobile: +420775259871 Parizksa 5, Praha 1 Prague Czech Republic Personal Website: http://www.mtkocak.com --047d7b3a8170a20b55052ed04678--