Re: PHP 6.0 Wishlist
| From: | Xuefer | Date: | Sat, 13 Aug 2005 15:06:55 +0000 |
| Subject: | Re: PHP 6.0 Wishlist | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-17973@lists.php.net to get a copy of this message | ||
On 8/13/05, Marco Tabini <marcot@tabini.ca> wrote:
>
> On 8/13/05 2:25 AM, "Ilia Alshanetsky" <ilia@prohost.org> wrote:
>
> > Why would I need name spaces for basic functions, just so that I need to
> > rename all my code to use str:replace rather then str_replace and
> > perform 2 hash table lookups?
> >
>
> Or maybe so that you don't have to look at the manual fifteen times a minute
> so that you can remember whether the needle goes before the haystack in a
> particular function or not.
>
> I'm not saying it's the perfect solution, but it's a good opportunity to
> clean things up a bit. Or it can be done in the global namespace and forget
> about namespaces altogether--I don't care much for them either, but I do
> think that consistent function naming and parameter ordering is an
> opportunity worth taking advantage of, that's all.
>
yeah, php is meant to be simple. php functions was sadly decided by
the each one who introduced it, with little standard applied. can u
imagine how many php scripters is checking manual right now?
+10 to solve the situation. but !@# 0 waiting for a good way without
breaking old scripts.
possibly make a internal or loadable "argument reposition table", enabled with:
declare(fix_function_argument_position);
fix at compile time, no performance lost on runtime.
but might confuse the debuger if the origin position in source is
forget after compile
can't help for class method as class is unknown at compile time