Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:81731 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 48219 invoked from network); 3 Feb 2015 19:18:07 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 3 Feb 2015 19:18:07 -0000 Authentication-Results: pb1.pair.com header.from=anatol.php@belski.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=anatol.php@belski.net; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain belski.net from 85.214.73.107 cause and error) X-PHP-List-Original-Sender: anatol.php@belski.net X-Host-Fingerprint: 85.214.73.107 klapt.com Received: from [85.214.73.107] ([85.214.73.107:54433] helo=h1123647.serverkompetenz.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F4/F5-20608-BEE11D45 for ; Tue, 03 Feb 2015 14:18:03 -0500 Received: by h1123647.serverkompetenz.net (Postfix, from userid 33) id 4E40B23D6002; Tue, 3 Feb 2015 20:18:00 +0100 (CET) Received: from 217.254.142.48 (SquirrelMail authenticated user anatol@belski.net) by webmail.klapt.com with HTTP; Tue, 3 Feb 2015 20:18:00 +0100 Message-ID: <5800006543ae6cc7beb477227f89af64.squirrel@webmail.klapt.com> In-Reply-To: <54D0DFE5.9030602@lsces.co.uk> References: <8C47FA53-0964-49C0-963C-332A936348A5@ajf.me> <54D00C40.8060907@lsces.co.uk> <54C5DC93-9600-4EE2-BF06-7BF10FC6AD5C@ajf.me> <54D08D50.5050407@lsces.co.uk> <1C2ED70C-72A0-4513-A134-5DAE4CCA5B3D@ajf.me> <54D0DFE5.9030602@lsces.co.uk> Date: Tue, 3 Feb 2015 20:18:00 +0100 To: "Lester Caine" Cc: internals@lists.php.net User-Agent: SquirrelMail/1.5.2 [SVN] MIME-Version: 1.0 Content-Type: text/plain;charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] [RFC] Big Integer Support From: anatol.php@belski.net ("Anatol Belski") Hi Lester, On Tue, February 3, 2015 15:49, Lester Caine wrote: > On 03/02/15 14:03, Andrea Faulds wrote: > >> But I don’t consider 0.25MB extra to be such a problem in practice. The >> > PHP binary is already huge, and every system running PHP will have ample > memory. > > Yes one approach is 'computers are getting faster with lots of memory' > ... and for servers this is not a problem ... they will more than > likely be 64bit anyway! But for smaller embedded devices php *IS* becoming I would like to ask, what those embedded devices are. Also I would like to state that it's hard to part the concerns you express. Arbitrary integer math is the daily bread of any modern programming language. Furthermore, from the test done so far there's no much visible impact to the present operation. Regards Anatol