Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:76966 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 24053 invoked from network); 30 Aug 2014 11:53:48 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 30 Aug 2014 11:53:48 -0000 Authentication-Results: pb1.pair.com header.from=php@beccati.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=php@beccati.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain beccati.com designates 176.9.114.167 as permitted sender) X-PHP-List-Original-Sender: php@beccati.com X-Host-Fingerprint: 176.9.114.167 spritz.beccati.com Received: from [176.9.114.167] ([176.9.114.167:53194] helo=mail.beccati.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 4E/81-09868-94BB1045 for ; Sat, 30 Aug 2014 07:53:47 -0400 Received: (qmail 26993 invoked from network); 30 Aug 2014 11:53:41 -0000 Received: from home.beccati.com (HELO ?192.168.1.202?) (88.149.176.119) by mail.beccati.com with SMTP; 30 Aug 2014 11:53:41 -0000 Message-ID: <5401BB3D.4060000@beccati.com> Date: Sat, 30 Aug 2014 13:53:33 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: Anatol Belski , Xinchen Hui CC: PHP Internals , Nikita Popov , Pierre Joye , Dmitry Stogov References: <2afc5a878ff4c780c74f4604f77525c1.squirrel@webmail.klapt.com> <8642f96d780f339c448bd330c6e1c097.squirrel@webmail.klapt.com> In-Reply-To: <8642f96d780f339c448bd330c6e1c097.squirrel@webmail.klapt.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Re: 64 bit string offsets From: php@beccati.com (Matteo Beccati) On 29/08/2014 23:58, Anatol Belski wrote: > On Fri, August 29, 2014 18:34, Xinchen Hui wrote: >> if a string is bigger than 2^32... I think there must be a bug.... :) >> > Only for this case you mean, or generally? As we safe with memory_limit > anyway. Even though size_t allows "huge" strings, would it be so bad to throw an error when one tries to create a string longer than 2^32 bytes, regardless of memory_limit? Cheers -- Matteo Beccati Development & Consulting - http://www.beccati.com/