Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:20376
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 25 Nov 2005 12:39:45 +0100
Message-ID: <00A2E2156BEE8446A81C8881AE117F192C1D08@companyweb>
Thread-Topic: [PHP-DEV] Re: PHP 5.1 (Or How to break tousands of apps outthere)
Thread-Index: AcXxs5Skqt3S5io+QMap+/KZTLAm7gAACdVA
To: "Derick Rethans" <derick@php.net>
Cc: <internals@lists.php.net>
Subject: AW: [PHP-DEV] Re: PHP 5.1 (Or How to break tousands of apps outthere)
From: mp@webfactory.de ("Matthias Pigulla")


> I didn't say that my code is more important, but if we don't=20
> get the date class now, we will get it in 5.1.1 and then=20
> break your code - so that doesn't really matter. THe only=20
> correct solution is to start prefixing the pear date class,=20
> as that needs to be done in the long run anyway.

Derick, this is not only about the PEAR date class but about pretty much
every larger PHP codebase/project. You don't seem to understand the
impact.

> No no, the core reserves the right to name whatever they=20
> want, it's the userland code that is responsible for=20
> prefixing their classes.

Actually I just decided to work through my 100,000 lines of code and
rename every class; for the sake of forwards compatibility, I'll
generate GUIDs for each class and keep a mapping table on my desktop.
Oh, and while I'm at it, I'll switch over to some other language as
well.

-mp.