Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:72646 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 18973 invoked from network); 17 Feb 2014 08:09:11 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 Feb 2014 08:09:11 -0000 Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 108.166.43.99 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 108.166.43.99 smtp99.ord1c.emailsrvr.com Linux 2.6 Received: from [108.166.43.99] ([108.166.43.99:60560] helo=smtp99.ord1c.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 3A/D9-56374-5A3C1035 for ; Mon, 17 Feb 2014 03:09:10 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp5.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 674271B0184; Mon, 17 Feb 2014 03:09:07 -0500 (EST) X-Virus-Scanned: OK Received: by smtp5.relay.ord1c.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 1A4F71B016F; Mon, 17 Feb 2014 03:09:07 -0500 (EST) Message-ID: <5301C3A2.3060506@sugarcrm.com> Date: Mon, 17 Feb 2014 00:09:06 -0800 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: Pierre Joye , PHP internals References: In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] my take on PHP 6, part 2 From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > https://wiki.php.net/ideas/php6 Here's a bunch of mine: - Clean up error reporting (let's decide - do we want exceptions? Warnings? Both?), make errors not so damn expensive and fix @ to be much more lean-and-mean than it is now. - Figure out named args. I think it's time. - Bringing mbstring, various submodules of intl and assorted other things under one roof as proper support for everything one needs with i18n and l10n (maybe part of "Unicode support") - Cleaning up resources handling so that various scenarios like "I freed resource in error handler and now my code segfaults" wouldn't happen. - Cleaning up LSP rules for inheritance checks, we still have some weird cases lurking there AFAIR - Plug serialize/dtor hole, it's really not good that unserializing data allows one to mess up with stuff. - Create a robust design for escaping stuff, so it would be clear what should be escaped, in which context and which encoding, etc. OK, I think enough for now :) -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227