Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:20250
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <BC.B5.11378.C9583834@pb1.pair.com>
To: internals@lists.php.net
Date: Tue, 22 Nov 2005 15:54:37 -0500
User-Agent: Mozilla Thunderbird 1.0.7-1.1.fc4 (X11/20050929)
MIME-Version: 1.0
References: <Pine.LNX.4.62.0511221852340.31280@localhost>	<B2.4B.11378.16163834@pb1.pair.com>	<Pine.LNX.4.62.0511221925250.31280@localhost> <195610836.20051122204314@marcus-boerger.de>
In-Reply-To: <195610836.20051122204314@marcus-boerger.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: PDM Meeting Notes
From: jrhernandez05@gmail.com (Jessie Hernandez)

Marcus,

I agree that we should work together on this, so that we can achieve the 
best result possible and to avoid duplicate work. To a certain degree, 
we have already worked together on this, when you suggested using the 
__autoload mechanism to resolve namespace imports and this is what I 
ended up doing.

I will try to add functions and constants soon to the patch, and will 
look at the PHP 6 source to see what I need to do to make it work with 
that version.


Regards,

Jessie



Marcus Boerger wrote:
> Despite the written sentence i had namespaces on my radar for a long time
> now. That i didn't do anything just reflects the current state of PHP. We
> are not going to have namespaces for a list of good reasons. Your patch
> and the amount of people asking for that feature started discussions all
> over again. So while beeing in paris we were able to look at the following
> things the stuff we knew your patch was supposed to do and the stuff we
> wanted your patch to do as well as the module patch and the stuff we thought
> that patch should do. After a long discussion we came to the intermediate
> conclusion that it is worth to restart working on namespaces again since a
> few issues we had with the first approach have been solved as of now.
> However the notes show that PHP will undergo a big amount of changes
> especially engine api wise. Thus i guess we won't start working on that
> beforehand. If you feel to do more work on your stuff then go ahead we
> might go with exactly your patch or ignore it completley when the changes
> are done. That's how PHP is done and has nothing to do whetehr i plan to do
> some work on my own. Indeed i could come up with a patch that would be
> outrules by yours or somebody elses as well. That's open source. Things
> might be ignored or removed or rewritten at any time by others. The
> advantage is that we can all work together if we feel like and that by doing
> so we cannot only learn from each other but reach a very good final result
> (if there is such a thing as final result in software).
> 
> To cut this short. As soon as i feel like i will start to do some work. And
> as soon as there is something to show i will post it. Since i always showed
> my stuff were early here. Should you do something earlier i think i will try
> to catch up with you and either say nothing to do for me left or send you my
> thoughts by mail or try to come up with my brand own ideas.
> 
> We'll see, nothing has been made a law by those notes.
> 
> marcus