Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:37289
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain cisco.com designates 144.254.224.140 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8A9E3.0DC1AB4D"
Date: Tue, 29 Apr 2008 12:22:53 +0200
Message-ID: <BADE85FDE9053E4AAEC411E40C77C2911A66AE@xmb-ams-33e.emea.cisco.com>
In-Reply-To: <462e563f0804290316p7549f104p9ec14dc4ff7b5606@mail.gmail.com>
Thread-Topic: [PHP-DEV] Class Properties in Interfaces?
Thread-Index: Acip4ij6iC1bJFRxQwCqvAHILxTsdAAAERBQ
References: <48169695.9040803@omegavortex.net> <339714303.20080429114607@marcus-boerger.de> <BADE85FDE9053E4AAEC411E40C77C2911A6693@xmb-ams-33e.emea.cisco.com> <462e563f0804290316p7549f104p9ec14dc4ff7b5606@mail.gmail.com>
To: <internals@lists.php.net>
Subject: RE: [PHP-DEV] Class Properties in Interfaces?
From: johncart@cisco.com ("John Carter -X (johncart - PolicyApp Ltd at Cisco)")

------_=_NextPart_001_01C8A9E3.0DC1AB4D
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

It might be bad design, but design is down to the application developer
and not the people who define a language.
=20
I'm not necessary asking for the feature, I just want to understand why
we can't do it.
=20
John.


________________________________

From: James Dempster [mailto:letssurf@gmail.com]=20
Sent: 29 April 2008 11:17
To: John Carter -X (johncart - PolicyApp Ltd at Cisco)
Cc: internals@lists.php.net
Subject: Re: [PHP-DEV] Class Properties in Interfaces?


I would start by saying it's bad design. you should use getters and
setters which you can define in you interface

--
/James


On Tue, Apr 29, 2008 at 11:07 AM, John Carter -X (johncart - PolicyApp
Ltd at Cisco) <johncart@cisco.com> wrote:


	Marcus,
=09
	I understand why Interfaces can't have bodies, but could you
explain why
	Interfaces can't have properties?
=09
	Thanks,
=09
	John.
=09

	-----Original Message-----
	From: Marcus Boerger [mailto:helly@php.net]
	Sent: 29 April 2008 10:46
	To: Jeremy Privett
	Cc: PHP Developers Mailing List
	Subject: Re: [PHP-DEV] Class Properties in Interfaces?
=09
	Hello Jeremy,
=09
	 interfaces cannot have properties, nor can they have method
bodies -
	that is the whole purpose of interfafces. We are thinking of
adding
	traits which would allow for both but would treat inheritance
	differently. Until we get that you would need to provide an
abstract
	interface to access data in the same way.
=09
	marcus
=09
	Tuesday, April 29, 2008, 5:31:33 AM, you wrote:
=09
	> Hey list,
=09
	> I was curious what everyone thought of implementing the
ability to
	> specify class members in interfaces. I've run into a couple of
	> circumstances where I would like to specify public member
names inside
=09
	> of an interface to ensure that these members are accessed in a
	> standard way and to ensure that they exist. Currently, trying
to
	> include them in an interface results in "*Fatal error*:
Interfaces may
=09
	> not include member variables in file/line number".
=09
	> Thoughts?
=09
	> Thanks.
=09
	> --
	> Jeremy Privett
	> C.E.O. & C.S.A.
	> Omega Vortex Corporation
=09
	> http://www.omegavortex.net
=09
	> Please note: This message has been sent with information that
could be
=09
	> confidential and meant only for the intended recipient. If you
are not
=09
	> the intended recipient, please delete all copies and inform us
of the
	> error as soon as possible. Thank you for your cooperation.
=09
=09
=09
=09
=09
	Best regards,
	 Marcus
=09
=09
	--
	PHP Internals - PHP Runtime Development Mailing List To
unsubscribe,
	visit: http://www.php.net/unsub.php
=09
=09
	--
	PHP Internals - PHP Runtime Development Mailing List
	To unsubscribe, visit: http://www.php.net/unsub.php
=09
=09



------_=_NextPart_001_01C8A9E3.0DC1AB4D--