Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:66682
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.52 as permitted sender)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <CALtuQzA0M80O3P3yrOqn-hWFk5+uCYoM+8rAqNK-f5e8CUwXyg@mail.gmail.com>
Date: Mon, 18 Mar 2013 10:17:06 +0000
Cc: Sebastian Krebs <krebs.seb@gmail.com>
Content-Transfer-Encoding: quoted-printable
Message-ID: <E2C1F5BB-DAC2-4D84-87F3-9385FDAEF103@gmail.com>
References: <CALtuQzA0M80O3P3yrOqn-hWFk5+uCYoM+8rAqNK-f5e8CUwXyg@mail.gmail.com>
To: PHP internals list <internals@lists.php.net>
Subject: Re: [PHP-DEV] Abstract properties
From: marcello.duarte@gmail.com (Marcello Duarte)

On 1 Dec 2012, at 12:34, Sebastian Krebs wrote:

> Hi,
>=20
> Don't want to start a big discussion, but is there a concrete reason, =
why
> abstract properties (or "a kind of abstract") are not supported?

Hi,

The reason for not having abstract properties is that when you are =
defining a type you don't care about how the implementation will store =
the state. The contract is about message exchanges, how the objects will =
talk to each other, via the public interface, e.g. the public methods.

Also, think of the keyword "abstract" as something that is incomplete. =
An abstract class is an incomplete class, an abstract method is an =
incomplete method. So an abstract property doesn't make sense, as it =
doesn't need anything to be complete.

Reinforce the implementation to store state in a particular way would be =
a bad feature for PHP. This is one the things we got it right.

Kind regards,
Marcello