Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:64580
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <50E8AA4D.5090207@sugarcrm.com>
References: <CAF+90c_girfbcPBb8rCV3bPNR2Hsd5gyRPB+VArCfqjPPqG5DQ@mail.gmail.com>
	<19D80B01-BE88-4119-8A15-B631A96060E5@mrclay.org>
	<CAF+90c9=HgRLHv4o=5dGkQzZPC5Q0tbPC8GD9AZ13Jwkr0pOcw@mail.gmail.com>
	<CAHjTTqOwrCfprcw3jCiLU21NygYCjrz+3+zpjdnU_sj-JbQonQ@mail.gmail.com>
	<50E8AA4D.5090207@sugarcrm.com>
Date: Sat, 5 Jan 2013 19:06:32 -0500
Message-ID: <CAAyV7nFW45f5vEUkZXhbgaJe=TL1Tbfp7igbUkQ=ifJc9tAsvQ@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Cc: Nikita Popov <nikita.ppv@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7b6d934033549004d2937cf0
Subject: Re: [PHP-DEV] [RFC] Alternative typehinting syntax for accessors
From: ircmaxell@gmail.com (Anthony Ferrara)

--047d7b6d934033549004d2937cf0
Content-Type: text/plain; charset=ISO-8859-1

Stas,


> I think this is way too much magic. This means default is no longer a
> default, but instead some obscure flag that somehow is carried over to
> the setter. I do not think redefining initialization as permitting nulls
> is a good idea, initialization and value set are two different things.


"Too much magic"? It's completely consistent with how method parameters
work now. In fact, I'd argue that introducing a new syntax for this would
be inconsistent with the current paradigm.

This becomes especially true if initializers are added, where the property
would be initialized to a non-null value. Hence adding the ability for it
to *never* actually *be* null in the first place...

Anthony

--047d7b6d934033549004d2937cf0--