Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:69210
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.179 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <20130918182518.GA12594@analysisandsolutions.com>
References: <BLU0-SMTP120B69BA7C5BC348F5D05DDE2390@phx.gbl>
	<20130917142758.GA26444@analysisandsolutions.com>
	<BLU0-SMTP4701BE02F35E19D8CCA6C37E2270@phx.gbl>
	<20130918175345.GA12155@analysisandsolutions.com>
	<BLU0-SMTP167E073F747D73BB304C951E2200@phx.gbl>
	<20130918182518.GA12594@analysisandsolutions.com>
Date: Wed, 18 Sep 2013 20:49:06 +0200
Message-ID: <CAGbiJu_hFLVXwa3b29fVq4JEsCyedgdQw8WVC8i3Kbjz4btK4A@mail.gmail.com>
To: Daniel Convissor <danielc@analysisandsolutions.com>
Cc: Bob Weinand <bobwei9@hotmail.com>, 
	Developers PHP Mailing List <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] Support for keywords where possible
From: dor.tchizik@gmail.com (Madara Uchiha)

>
> Hi Bob:
>
> > Well, that makes no sense. Then you just could say no to all new
> > language changes.  Because it cannot be run on older versions.
>
> Allow me one last post to clarify.  What I said is the cost in _this_
> case doesn't outweigh the advantages.
>
> As someone who writes a lot of open source (and proprietary) code that
> gets run on machines that I have no control over, implementing this
> proposal will complicate my life.  Every time I make a function I'll
> have to ask myself "is this a reserved word in older versions of PHP?"
>
> I'll leave the discussion at that.
>
> Thanks,
>
> --Dan

Really? Really?! If you don't want to use (un)reserved keywords, just
don't, regardless of if it's allowed in PHPX and not in PHPY, why do
you care if it's implemented for those who do want it available?