Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:65138
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.219.54 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <51005B7F.6060209@googlemail.com>
References: <510038C9.5000900@mrclay.org>
	<B103E205-5F44-4524-9BCD-7BF241F7E552@zerocue.com>
	<CAFMT4Nq+27=7BuqrJggjjf8mT_NBAXr7v-qzkWazFgdQLYTRew@mail.gmail.com>
	<51005B7F.6060209@googlemail.com>
Date: Wed, 23 Jan 2013 18:12:54 -0700
Message-ID: <CAFMT4NoHeTM40W=tn7Rp3nDdjEiKWsYFPtcLNQroHom83WSvYQ@mail.gmail.com>
To: Crypto Compress <cryptocompress@googlemail.com>
Cc: internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] C# properties vs. accessors RFC
From: morrison.levi@gmail.com (Levi Morrison)

>> I also don't like the `?` for `nullable`.  Just stick with PHP
>> convention and do:
>>
>>      class Foo {
>>          public Bar $bar = NULL;
>>      }
>
>
> There is no such PHP convention. The PHP convention is *not restrict type*
> (+"loosely typed" addons).
> So NULL is automatically allowed.

For properties, yes, but the idea it stems from is type-hints. Given
the following type-hint, passing a null is not allowed:

    class Foo {
      function bar(Bar $bar) {}
    }

Whereas in the following NULL is allowed:

    class Foo {
      function bar(Bar $bar = NULL) {}
    }

This is what I mean by the PHP convention for allowing NULL.