Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:17406 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 93577 invoked by uid 1010); 26 Jul 2005 08:31:39 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 93466 invoked from network); 26 Jul 2005 08:31:38 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 26 Jul 2005 08:31:38 -0000 X-Host-Fingerprint: 81.169.182.136 ajaxatwork.net Linux 2.4/2.6 Received: from ([81.169.182.136:48413] helo=strato.aixcept.de) by pb1.pair.com (ecelerity 2.0 beta r(6227M)) with SMTP id 79/61-58254-630F5E24 for ; Tue, 26 Jul 2005 04:11:35 -0400 Received: from [192.168.1.3] (dsl-082-083-224-172.arcor-ip.net [82.83.224.172]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by strato.aixcept.de (Postfix) with ESMTP id 2C14B35C36E; Tue, 26 Jul 2005 10:29:08 +0200 (CEST) Date: Tue, 26 Jul 2005 10:11:37 +0200 Reply-To: Marcus Boerger X-Priority: 3 (Normal) Message-ID: <03165207.20050726101137@marcus-boerger.de> To: Weyert de Boer Cc: Jessie Hernandez , internals@lists.php.net In-Reply-To: <42E5EE8C.3030609@innerfuse.biz> References: <52.31.61486.E8DCDD24@pb1.pair.com> <1122328113.647.16.camel@boost.home.ahk> <34.C6.58254.4BD75E24@pb1.pair.com> <1958582676.20050726092603@marcus-boerger.de> <42E5EE8C.3030609@innerfuse.biz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [PATCH] Namespace Patch, Alpha 3 From: mail@marcus-boerger.de (Marcus Boerger) Hello Weyert, Tuesday, July 26, 2005, 10:04:28 AM, you wrote: > Hello, > How can I use the namespaces support, in such way that I can use with my > coding guideline? > interfaces -> interface.NAME.inc.php > classes -> class.NAME.inc.php > It doesn't seem it's possible now, because it's hard coded against > NAME.php. Oh well, I might will have > a look at it, and try to come with some workable, with support for > nameless namespaces, etc. I have the same probelm and don't see any reason in a hard coded naming scheme unless be it a default fallback. Look at my other reply. Best regards, Marcus