Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:91615
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.49 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <56E16B42.60908@gmail.com>
References: <1F.91.55238.41F10D65@pb1.pair.com>
	<FA.10.10408.29514D65@pb1.pair.com>
	<56D42CD3.6020602@gmail.com>
	<DB.E1.07778.3D165D65@pb1.pair.com>
	<56D57DF4.8000906@gmail.com>
	<56D5D2AD.6070805@gmail.com>
	<56D5DDA6.4080607@fleshgrinder.com>
	<40.73.36499.548B6D65@pb1.pair.com>
	<56D6BBD0.5010505@gmail.com>
	<56D73386.3000903@fleshgrinder.com>
	<86.68.21983.A2508D65@pb1.pair.com>
	<56D86C00.6000904@fleshgrinder.com>
	<12.FB.08749.AF759D65@pb1.pair.com>
	<56DAC26C.50304@fleshgrinder.com>
	<56DAE00F.2030203@lsces.co.uk>
	<56DAF480.7030508@fleshgrinder.com>
	<CAMPTd_B6VNQymDJo2MX03KrOWd1Mcfjg6gNY=GO1swxV8snrKQ@mail.gmail.com>
	<0B.E0.29316.019CBD65@pb1.pair.com>
	<56DBFDB5.1010806@fleshgrinder.com>
	<43.5B.29316.A864DD65@pb1.pair.com>
	<56DD64F5.5010503@gmail.com>
	<D7.70.03587.1B0AED65@pb1.pair.com>
	<56DEA829.5030903@gmail.com>
	<2D.96.15119.232FFD65@pb1.pair.com>
	<CAKnqCEZMh-P8XmAeQtdPnw4ZaZGb4=wmm_9QYZPhtuPUwaXLCA@mail.gmail.com>
	<76.21.53667.08C41E65@pb1.pair.com>
	<56E16B42.60908@gmail.com>
Date: Thu, 10 Mar 2016 09:44:45 -0600
Message-ID: <CAH=AbGJVjnrZr8KHTWkNkiA6KgvrZKnTpGDQxD74fqT1x5vdbw@mail.gmail.com>
To: Rowan Collins <rowan.collins@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11395a22978521052db3b1d2
Subject: Re: [PHP-DEV] [RFC Proposal] var keyword deprecation/removal
From: browner12@gmail.com (Andrew Brown)

--001a11395a22978521052db3b1d2
Content-Type: text/plain; charset=UTF-8

as @Arvids said, var is missing functionality that public has, so they are
not exact aliases of each other. i think this is valid enough reason to
remove it.

even if it weren't the case, I would say let the language maintainers
decide if this cleanup would be worth it to them and make their lives
easier and their code more consistent, and userland developers (including
myself) be damned in 5+ years with this minor inconvenience. I think 5
years is plenty of lead time to make this fix.

I'm with @James. I'm getting sick of listening to the same argument over
and over. Put it to a vote, and accept whatever happens.


-- 
Andrew Brown

--001a11395a22978521052db3b1d2--