Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:78063 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 88339 invoked from network); 14 Oct 2014 20:47:45 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 Oct 2014 20:47:45 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 108.166.43.115 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 108.166.43.115 smtp115.ord1c.emailsrvr.com Linux 2.6 Received: from [108.166.43.115] ([108.166.43.115:45071] helo=smtp115.ord1c.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 0B/B5-18603-FEB8D345 for ; Tue, 14 Oct 2014 16:47:44 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp7.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id BEE033806D2; Tue, 14 Oct 2014 16:47:40 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp7.relay.ord1c.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 779AF3806EE; Tue, 14 Oct 2014 16:47:40 -0400 (EDT) X-Sender-Id: smalyshev@sugarcrm.com Received: from Stass-MacBook-Pro.local ([UNAVAILABLE]. [74.85.23.222]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA) by 0.0.0.0:465 (trex/5.2.13); Tue, 14 Oct 2014 20:47:40 GMT Message-ID: <543D8BEB.8000803@sugarcrm.com> Date: Tue, 14 Oct 2014 13:47:39 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: Andrea Faulds CC: PHP Internals References: <8C47FA53-0964-49C0-963C-332A936348A5@ajf.me> <543CE41B.5020308@sugarcrm.com> <543D5C78.9040905@sugarcrm.com> <3FB11875-5FEC-4CC1-BA13-D910F588D252@ajf.me> <543D6761.90201@sugarcrm.com> <630973F6-C5E7-4EE2-A7E4-46A1CC88A082@ajf.me> <543D6DFB.9050806@sugarcrm.com> <303FAFBC-7AEA-49A8-8A7D-67E66BF23E60@ajf.me> In-Reply-To: <303FAFBC-7AEA-49A8-8A7D-67E66BF23E60@ajf.me> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] [RFC] Big Integer Support From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > You throw an error. Just as plenty of functions already can’t handle > ridiculously large integer arguments. The problem is, if you function can handle the int range and you checked for is_int() and everything worked fine - now it's broken because is_int() no longer implies fixed range and there's no way to check if you're dealing with fixed-range number or infinite-range number. > No, it does: There are now integers, and objects that represent large > integers, which behave differently. IS_INT and IS_BIGINT would necessarily behave differently too - since some functions may support both and some only integers. Again, no change here. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/