Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:20911
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
To: "'PHP Developers Mailing List'" <internals@lists.php.net>
Date: Wed, 30 Nov 2005 22:47:06 +0100
Message-ID: <002d01c5f5f7$9be41330$9a00a8c0@stade.topconcepts.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Thread-Index: AcX195vARyUtm3OFT9CAx2jpFaZbRA==
Subject: PDM Meeting Notes
From: ruempler@topconcepts.com (=?iso-8859-1?Q?S=F6nke_Ruempler?=)

Hi,

maybe you guys are tired of namespace and G*** discussions, so I'd like to
announce some ideas and toughts about the PDM notes:

> 2.13 Case sensitivity of identifiers

Maybe this could throw some E_STRICT deprecated warning and PHP7 goes
completely case sensitive.

> 5.7 Using an undefined property in a class with defined
> properties should
> throw a warning

> Conclusions:
> 
>    1. We will not start throwing any notice for this.

Here I see some inconsistency. As of PHP5 static and const where introduced
into the class model. Accessing undefined static class variables or class
constants is E_FATAL. I thought accessing undefined properties in PHP5 is
for some BC. In PHP6 IMHO this should be consistent for static, const and
"normal" properties. If someone likes to set and get undefined properties he
can make use of overload/interceptors.

Some more argument is that the new OOP features allow us to delevop more
strictly (interfaces, type hints, abstract, final etc.). All this features
are only helpers for us and we could live without them if we were perfect,
but we aren't and as of that fact I personally like strict programming PHP5,
using type hints, interfaces, assert() etc. (and being E_FATAL'ed).


Just my two cent - for the other points: +1 :)

Best regrards.