Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:64537
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.43 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <19D80B01-BE88-4119-8A15-B631A96060E5@mrclay.org>
References: <CAF+90c_girfbcPBb8rCV3bPNR2Hsd5gyRPB+VArCfqjPPqG5DQ@mail.gmail.com>
	<19D80B01-BE88-4119-8A15-B631A96060E5@mrclay.org>
Date: Sat, 5 Jan 2013 01:48:14 +0100
Message-ID: <CAF+90c9=HgRLHv4o=5dGkQzZPC5Q0tbPC8GD9AZ13Jwkr0pOcw@mail.gmail.com>
To: Steve Clay <steve@mrclay.org>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=f46d04083e337e9e4704d27ff33d
Subject: Re: [PHP-DEV] [RFC] Alternative typehinting syntax for accessors
From: nikita.ppv@gmail.com (Nikita Popov)

--f46d04083e337e9e4704d27ff33d
Content-Type: text/plain; charset=ISO-8859-1

On Sat, Jan 5, 2013 at 12:31 AM, Steve Clay <steve@mrclay.org> wrote:

> Would the following two be exactly functionally equivalent?
>
> public Foo $foo;
>
> public $foo {
>     get;
>     set(Foo $value) { $this->foo = $value; }
> }
>
> We should also consider how an author would allow type-hinted properties
> to accept NULL as a new value, in both proposals.
>

I think that's a very interesting question, thanks for bringing it up. I
think a good approach here would be the same one used for function argument
typehints, i.e. allow NULL when NULL is specified as the default value. So
`public DateTime $date;` would not allow an explicit NULL assignment,
whereas `public DateTime $date = NULL;` would.

Nikita

--f46d04083e337e9e4704d27ff33d--