Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:24245 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 71824 invoked by uid 1010); 3 Jul 2006 13:36:05 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 71809 invoked from network); 3 Jul 2006 13:36:05 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 3 Jul 2006 13:36:05 -0000 X-Host-Fingerprint: 195.225.34.5 fw01.axit.nl Received: from ([195.225.34.5:2614] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.3 r(11751M)) with ESMTP id 80/0F-13848-44D19A44 for ; Mon, 03 Jul 2006 09:36:04 -0400 Message-ID: <80.0F.13848.44D19A44@pb1.pair.com> To: internals@lists.php.net Date: Mon, 3 Jul 2006 15:32:24 +0200 Lines: 11 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 X-RFC2646: Format=Flowed; Original X-Posted-By: 195.225.34.5 Subject: Php_ and Spl_ classname prefixes? From: r.korving@xit.nl ("Ron Korving") In the light of PHP6, could it be an interesting idea to rename all classes and interfaces to use prefixes like Php_ and Spl_ ? This way there can be a Php_Date class for example, while keeping everybody happy. Migration issues for people should be quite limited. Or is this whole suggestion futile because of the new namespace implementation? - Ron