Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:65147
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 209.85.217.171 as permitted sender)
Message-ID: <51013AE2.1030804@googlemail.com>
Date: Thu, 24 Jan 2013 14:45:06 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: internals@lists.php.net
References: <510038C9.5000900@mrclay.org> <B103E205-5F44-4524-9BCD-7BF241F7E552@zerocue.com> <CAFMT4Nq+27=7BuqrJggjjf8mT_NBAXr7v-qzkWazFgdQLYTRew@mail.gmail.com> <51005B7F.6060209@googlemail.com> <CAFMT4NoHeTM40W=tn7Rp3nDdjEiKWsYFPtcLNQroHom83WSvYQ@mail.gmail.com>
In-Reply-To: <CAFMT4NoHeTM40W=tn7Rp3nDdjEiKWsYFPtcLNQroHom83WSvYQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] C# properties vs. accessors RFC
From: cryptocompress@googlemail.com (Crypto Compress)

Am 24.01.2013 02:12, schrieb 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.

Hello Levi,

you absolutly right. I was confused by the syntax. This properties are 
normal
methods and should behave the same. Mixing "initialize-with-NULL" and
"optional/nullable" is somewhat messy though.

cryptocompress