Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:64842
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.219.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAMyk_AaH-u09zAdzdkih83BOdBWyxs_uH5ty52=rYDSURbweJA@mail.gmail.com>
References: <CAF+90c_girfbcPBb8rCV3bPNR2Hsd5gyRPB+VArCfqjPPqG5DQ@mail.gmail.com>
 <CAF+90c9=HgRLHv4o=5dGkQzZPC5Q0tbPC8GD9AZ13Jwkr0pOcw@mail.gmail.com>
 <4ED7146272E04A47B986ED49E771E347BB3D6ABCB3@Ikarus.ameusgmbh.intern>
 <50EC5F8F.8010703@mrclay.org> <CAF+90c96OZcBfDEQDEwHVEG78HTirhKONXczEhZUvxQg10MNhA@mail.gmail.com>
 <CAMyk_AaH-u09zAdzdkih83BOdBWyxs_uH5ty52=rYDSURbweJA@mail.gmail.com>
Date: Thu, 10 Jan 2013 22:30:44 -0500
Message-ID: <CAFp73XtoXe=Qk_aKp4aXQi7CtAnUmCJq1TL2B-YOD2CUnsiLBg@mail.gmail.com>
To: Lazare Inepologlou <linepogl@gmail.com>
Cc: Nikita Popov <nikita.ppv@gmail.com>, Steve Clay <steve@mrclay.org>, 
	PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=bcaec54d3ed2e62e9504d2faec5f
Subject: Re: [PHP-DEV] [RFC] Alternative typehinting syntax for accessors
From: guilhermeblanco@gmail.com ("guilhermeblanco@gmail.com")

--bcaec54d3ed2e62e9504d2faec5f
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

We all agree that nullable properties need to be addressed.
Now why just don't discuss a possible syntax and move on?
Initializers, parenthesis around unsetters, etc can all be detailed and
discussed later.

Here are the proposed syntaxes:

public DateTime? $date {
  get { ... }
  set { ... }
}

public DateTime $date =3D null {
  get { ... }
  set { ... }
}

public DateTime $date {
  get { ... }
  set($value =3D null) { ... }
}

public $date {
  get { ... }
  set(DateTime $value =3D null) { ... }
}


Now choose your options from 1-4 and move on...
Sometimes you truly love to discuss instead of act. Tsc, tsc, tsc...


Cheers,


On Thu, Jan 10, 2013 at 7:24 PM, Lazare Inepologlou <linepogl@gmail.com>wro=
te:

> Nikita,
>
>
> 2013/1/10 Nikita Popov <nikita.ppv@gmail.com>
>
> > On Tue, Jan 8, 2013 at 7:03 PM, Steve Clay <steve@mrclay.org> wrote:
> >
> > > On 1/8/13 2:56 AM, Christian Stoller wrote:
> > >
> > >> But the way 'nullable' properties are defined is not very intuitive
> and
> > >> unclean, in my opinion. Stas has already mentioned that.
> > >> `public DateTime $date =3D NULL;` // this looks like the property is
> > >> initialized with null, but it does not show that the property is
> > 'nullable'
> > >>
> > >
> > > Much agreed. After instantiation, these shouldn't behave differently:
> > >
> > > public     $foo =3D null;
> > > public Foo $foo =3D null;
> > >
> > > Sure, method signatures have special behavior based on a default valu=
e,
> > > but IMO:
> > > 1. those semantics aren't entirely intuitive to begin with
> > > 2. property initializers aren't method sigs
> > > 3. the semantics would apply only to some properties
> > >
> > >
> > >
> > >       public DateTime? $date;
> > >>
> > >> In C# the question mark after a type is a short hand for a generic
> > >> Nullable type.
> > >>
> > >
> > > I like that it's an established practice of doing exactly what we're
> > > trying to do.
> > >
> > > Could we not just make it obvious?:
> > >
> > > public Foo|null $foo;
> > >
> >
> > I updated the RFC to include the current state regarding default value
> and
> > nullability:
> >
> >
> https://wiki.php.net/rfc/propertygetsetsyntax-alternative-typehinting-syn=
tax
> >
> > One question that still needs to be discussed is what syntax regarding
> > parentheses we want to use if this makes it. Currently both set { } and
> > set($foo) { } style accessors are supported. Do we want to keep those t=
wo
> > with the new syntax?
> >
> > Nikita
> >
> > PS: I hope I'm not interrupting all those heated annotations discussion
> too
> > much ^^
> >
>
>
>
> In the RFC, one thing is not clear: How to provide typehints for nullable
> properties that actually have accessors.
>
> Will it be like this?
>
> public DateTime $date =3D null {
>   get { ... }
>   set { ... }
> }
>
>
>
>
> Lazare INEPOLOGLOU
> Ing=C3=A9nieur Logiciel
>



--=20
Guilherme Blanco
MSN: guilhermeblanco@hotmail.com
GTalk: guilhermeblanco
Toronto - ON/Canada

--bcaec54d3ed2e62e9504d2faec5f--