Re: Namespaces in PHP 6 - ++$take
| From: | Rasmus Lerdorf | Date: | Sat, 11 Nov 2006 13:37:19 +0000 |
| Subject: | Re: Namespaces in PHP 6 - ++$take | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-26516@lists.php.net to get a copy of this message | ||
I am not sure why this thread was revived. We decided long ago that we
would have namespaces in PHP 6 barring any nasty technical problems and
assuming a good way to implement it could be found.
And I'll second Tony here and mention that we really could use more
eyeballs on the bug database. I am sure everyone reading internals has
at least one part of PHP they know really well and it would be extremely
helpful if you could all pick a topic and watch for bugs related to that
topic. It's not hard to see just the bugs you care about. For all the
open Postgresql Related bugs, for example:
http://bugs.php.net/search.php?limit=50&order_by=id&direction=DESC&cmd=display&bug_type%5B%5D=PostgreSQL+related&status=Open
Or if you prefer to have them show up in your RSS reader, just put rss
in front of the search.php script there:
http://bugs.php.net/rss/search.php?limit=50&order_by=id&direction=DESC&cmd=display&bug_type%5B%5D=PostgreSQL+related&status=Open
Go to http://bugs.php.net/search.php for a list of all
the available
categories or even better, just watch for all bugs coming in and attack
the ones you think you might have a clue on.
http://bugs.php.net/rss/search.php?direction=DESC&status=Open&cmd=display
You don't necessarily have to be able to fix them in the C code, just
helping to get rid of bogus reports or translating the really bad
reports into a simple reproducable test case is often the part that
takes the most time. Once we have a 3-5 line reproducing script, the
fix is usually easy.
-Rasmus