Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:64579 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 37513 invoked from network); 5 Jan 2013 23:50:27 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 Jan 2013 23:50:27 -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 67.192.241.147 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 67.192.241.147 smtp147.dfw.emailsrvr.com Linux 2.6 Received: from [67.192.241.147] ([67.192.241.147:47881] helo=smtp147.dfw.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C3/7E-62408-14CB8E05 for ; Sat, 05 Jan 2013 18:50:26 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp31.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 220B75038A; Sat, 5 Jan 2013 18:50:23 -0500 (EST) X-Virus-Scanned: OK Received: by smtp31.relay.dfw1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id A8A26502FB; Sat, 5 Jan 2013 18:50:22 -0500 (EST) Message-ID: <50E8BC3E.4030705@sugarcrm.com> Date: Sat, 05 Jan 2013 15:50:22 -0800 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: =?UTF-8?B?SsOhY2h5bSBUb3XFoWVr?= CC: "internals@lists.php.net" References: <50E742A7.9010909@sugarcrm.com> <50E8A99F.5000900@sugarcrm.com> <50E8BA82.5000700@sugarcrm.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] How to get a PHP bug fixed? From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > I don't understand. There already IS the 'args' field where huge > objects also can be (and very often are). The new 'object' field > does not make any difference in this regard. It adds another place where huge objects can be - and unlike args, it is guaranteed to be an object, and those tend to be big. So chances to blow up the memory with this function become higher. That's why other functions gained parameters to amend this situation some time ago, this one would be good to add it too. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227