Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:60282
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <9570D903A3BECE4092E924C2985CE48555BEC3C2@MBX202.domain.local>
References: <9570D903A3BECE4092E924C2985CE48555BEC3C2@MBX202.domain.local>
Date: Tue, 24 Apr 2012 11:40:14 -0400
Message-ID: <CAAyV7nFbw-nK4z4K3Tva-Z6eCVqm8UJzFuvi8VSO61TxzTYhvA@mail.gmail.com>
To: Clint M Priest <cpriest@zerocue.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] RFC: Property get/set syntax (added isset/unset and references)
From: ircmaxell@gmail.com (Anthony Ferrara)

Clint,

Additionally, one more comment related to the read-only and
write-only.  I noticed that you're using E_ERROR for improper access.
Obviously you don't want this to be a warning, as the execution
shouldn't continue because that would be undefined.  However, what
about setting it to E_RECOVERABLE_ERROR, so that it can be captured
and recovered from...?  The engine wouldn't be in an unstable state,
so if we install an error_handler that throws an exception, there's no
reason to force-terminate the application...

I guess I'm just adverse to using E_ERROR except for cases where it's
literally not safe to continue (usually because the engine is put in
an inconsistent state)...

Anthony

On Tue, Apr 24, 2012 at 8:31 AM, Clint M Priest <cpriest@zerocue.com> wrote=
:
> I've updated the RFC to include details on adding isset/unset as well as =
references, detailed below:
>
> isset/unset:
>
> class TimePeriod {
> =A0 =A0private $Seconds =3D 3600;
>
> =A0 =A0public $Hours {
> =A0 =A0 =A0 =A0get { return $this->Seconds / 3600; }
> =A0 =A0 =A0 =A0set { $this->Seconds =3D $value; }
> =A0 =A0 =A0 =A0isset { return !is_null($this->Seconds); }
> =A0 =A0 =A0 =A0unset { $this->Seconds =3D NULL; }
> =A0 =A0}
> }
>
> References:
>
>
> class SampleClass {
>
> =A0 =A0private $_dataArray =3D array(1,2,5,3);
>
>
>
> =A0 =A0public $dataArray {
>
> =A0 =A0 =A0 =A0&get { return &$this->_dataArray; }
>
> =A0 =A0}
>
> }
>
>
>
> $o =3D new SampleClass();
>
> sort($o->dataArray);
>
> /* $o->dataArray =3D=3D array(1,2,3,5); */
>
> Comments?
>
> These would also include automatic implementations which call the respect=
ive functions on the backing field. =A0I could see only allowing isset/unse=
t automatic implementations if get/set were also specified as automatic imp=
lementations.
>
> Default implementations of isset/unset
>
> I'm also fielding comments/ideas on a way to always provide automatic imp=
lementations of isset/unset for any accessor that didn't define one automat=
ically. =A0One idea was for the isset (unspecified implementation) which wo=
uld return true if the getter provided any value which evaluated to true, s=
uch as this:
>
> class TimePeriod {
> =A0 =A0private $Seconds =3D 3600;
>
> =A0 =A0public $Hours {
> =A0 =A0 =A0 =A0get { return $this->Seconds / 3600; }
> =A0 =A0 =A0 =A0set { $this->Seconds =3D $value; }
> =A0 =A0}
> }
> /* Default Implementation Concept */
>
> =A0 =A0 =A0 =A0isset { return (int)$this->Hours; }
> =A0 =A0 =A0 =A0unset { $this->Hours =3D NULL; }
>
> Note that the automatic implementation of unset is not strictly the same =
as an unset() but without any sort of unset implementation a call to unset(=
) would do nothing. =A0Alternatively we could throw an error to a call on i=
sset and/or unset against a property which didn't define an implementation.
>
> Thoughts?
>
> -Clint