Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:17932 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 35699 invoked by uid 1010); 13 Aug 2005 00:11:38 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 35684 invoked from network); 13 Aug 2005 00:11:38 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 Aug 2005 00:11:38 -0000 X-Host-Fingerprint: 64.233.184.197 wproxy.gmail.com Linux 2.4/2.6 Received: from ([64.233.184.197:42407] helo=wproxy.gmail.com) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 59/71-33075-9BA3DF24 for ; Fri, 12 Aug 2005 20:11:38 -0400 Received: by wproxy.gmail.com with SMTP id i22so676257wra for ; Fri, 12 Aug 2005 17:11:33 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=KzrZgF2ivraWUWSjA02fAG+VlVLy/VeZfp3pT11vZDlwAoXWYVaiJCUZzYPMdSMwT0bAKIRCgSCkHskrB865HvA8rUE1wBfqNhs0EPQEMOSXRb3ZZUMSd5yethS6wGu6r/ej8VQmrX06zft0KJoz69Hz5KUFzuswdaY/1FZ0ljA= Received: by 10.54.37.64 with SMTP id k64mr2249564wrk; Fri, 12 Aug 2005 17:11:33 -0700 (PDT) Received: by 10.54.153.5 with HTTP; Fri, 12 Aug 2005 17:11:33 -0700 (PDT) Message-ID: <4e89b42605081217113def0f18@mail.gmail.com> Date: Fri, 12 Aug 2005 20:11:33 -0400 To: Sara Golemon Cc: internals@lists.php.net In-Reply-To: <00f301c59f83$10201f80$5c8be5a9@ohr.berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <42FCE0E4.604@lerdorf.com> <00f301c59f83$10201f80$5c8be5a9@ohr.berkeley.edu> Subject: Re: [PHP-DEV] Re: PHP 6.0 Wishlist From: kingwez@gmail.com (Wez Furlong) We definitely need to start thinking forward and introduct a 64-bit type. It needn't replace the 32-bit type. IIRC, Andi promised that we would have this after 5.1, so I think it's a done deal. It's especially important now that we have a number of extensions returning 64-bit data. And with Visual Studio .Net 2005, time_t is now 64-bit (!?) --Wez. On 8/12/05, Sara Golemon wrote: > > How about doubling integer precision to 64 bits and float/double precis= ion > > to 128 bits? It's in line with 64 bit CPU capabilities, and personally,= I > > wouldn't mind it a bit if it would make numerical processing in PHP slo= wer > > on 32 bit systems. I think the advantages are much too great for that. = If > > this is ever gonna happen, I think PHP6 would be great timing for it. > > > If there were such a type as 'zend_long' used universally that might be a= t > least possible (even configurable as a compile-time switch), but as it is > *EVERYTHING* that touches a zval expects a long. On 32bit platforms that= 's > a 32-bit number and there's no trivial way to change that. >=20 > Athlon64s and Opterons are cheap nowadays anyway. I picked up a MB/CPU > combo at Fry's last week for like $200. >=20 > -Sara >=20 > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php >=20 >