Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:17918
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <DC.91.33075.74DFCF24@pb1.pair.com>
To: internals@lists.php.net
References: <42FCE0E4.604@lerdorf.com>
Date: Fri, 12 Aug 2005 21:49:15 +0200
Lines: 76
Subject: Re: PHP 6.0 Wishlist
From: r.korving@xit.nl ("Ron Korving")

Now I'm not the person with the kind of karma that should make you guys
listen, but in case you are interested, I'll just add my 2 cents

> 1. Remove register_globals completely

+1

> 2. Remove magic_quotes_*

+1000

> 6. Remove some stuff that has been marked deprecated since PHP 3/4

+1

> A couple of others that we could consider, but I don't actually think
> wins us much apart from academic purity (which I have never been all
> that keen on) are:
>
> 7. Make identifiers case-sensitive

+1
Althought perhaps it could remain case-insensitive, but throwing a notice.
This way users can decide for themselves if they wanna write neat code by
using E_ALL. On the other hand, I assume case sensitivity would improve
overall performance, while notices do the exact opposite.

> 8. Remove various function aliases

+1

> -Rasmus

Might I add a few requests:

9. Much improved __toString behavior (I doubt I'd need to clarify that)

10. Broader support for (custom) stream-wrappers (I noticed the zlib
functions don't accept them). I wanted to make a stream wrapper for strings,
so I could do this: readgzfile("str://andHereSomeGzipData").. In fact, if
you ask me, such a str:// wrapper may be implemented as a standard wrapper.
It would be useful in a lot more cases where functions read from files.

11. Altered/improved garbage collection (see my recent post on leaking
memory when throwing exceptions from a foreach() loop). Leaking memory may
be perfectly fine in a webserver situation, but I personally use PHP a lot
for cli-scripts (sometimes forever-running daemon applications) and I'm sure
a lot of other people do as well.

12. I hate to bring this up, don't shoot me for this, but ... multiple
inheritance? ;)

13. A built-in code optimizer. Why should something like Zend optimizer be
installed afterwards, if everybody can use increased performance?

14. Turn (all) fatal errors in extentions and the core into exceptions.
Personally, I'd like to be able to catch and log all error situations, not
just the ones I create myself. The exceptions should be of a specific custom
exception class of course. If people don't catch the exceptions, the output
would be pretty much as the same as fatal errors are right now anyway, so BC
won't really be a problem.

15. Remove $HTTP_* (altho you may have included that when you thought of #6)
and register_long_arrays.

16. Support for <?php="foo" ?>

17. A reliable non-bankers-round function

18. The ability to use an array() of constants in a define.

Maybe I'll think of more later ;)

Ron