Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:18604 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 5987 invoked by uid 1010); 31 Aug 2005 13:37:59 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 5971 invoked from network); 31 Aug 2005 13:37:59 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 31 Aug 2005 13:37:59 -0000 X-Host-Fingerprint: 212.238.144.71 korving.demon.nl Received: from ([212.238.144.71:2657] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 97/90-15098-7B2B5134 for ; Wed, 31 Aug 2005 09:37:59 -0400 Message-ID: <97.90.15098.7B2B5134@pb1.pair.com> To: internals@lists.php.net References: <42FCE0E4.604@lerdorf.com> Date: Wed, 31 Aug 2005 15:37:51 +0200 Lines: 35 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Posted-By: 212.238.144.71 Subject: Re: PHP 6.0 Wishlist From: r.korving@xit.nl ("Ron Korving") It's unclear to me what the position of the big kahuna's is on the following issues, but I hope they can become a reality in PHP6: 1) named parameters. in user functions, but also in core functions: $result = in_array(needle: "foo", haystack: $array); 2) error reporting using exceptions. I would like it if I could catch PHP-errors and take appropriate action (such as logging it to a database or whatever). 3) doubling the precision of integers to 64 bits and floats to 128 bits. I know Wez wants this too, but will it happen? I think it would be nice if it would be a transparant change and the standard types would simply have a bigger range. 4) improved __toString behavior 5) 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). 6) 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. Thanks, Ron