Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:32816
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain omniti.com designates 66.225.209.50 as permitted sender)
DomainKey-Status: good
DomainKey-Signature: q=dns; a=rsa-sha1; c=nofws;
	s=test; d=omniti.com;
	h=Authentication-Results:Received:In-Reply-To:References:Mime-Version:Content-Type:Message-Id:Cc:Content-Transfer-Encoding:From:Subject:Date:To:X-Mailer;
	b=Z3OyAmifawSA1HGMDj7Ynpfup6fXH7EJwFbLa9P06M/8tXW/c0dDKL8opv16rQVF
	4FDCP+1TCmuM6E3XScDdfsQzqMRExv7AB3GhpWYVB5qOfAaU684Mj9jZcUxUTZEn
In-Reply-To: <200710160844.03049.seanius@seanius.net>
References: <64ED731E-CA44-498E-9AF9-C9B00037B863@omniti.com> <4713A637.7070100@zend.com> <200710160844.03049.seanius@seanius.net>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-ID: <8A692161-FAFD-40BA-B759-3746122FE25D@omniti.com>
Cc: internals@lists.php.net,
 Stanislav Malyshev <stas@zend.com>
Content-Transfer-Encoding: 7bit
Date: Tue, 16 Oct 2007 10:37:57 -0400
To: sean finney <seanius@seanius.net>
Subject: Re: [PHP-DEV] Large file support for PHP
From: wez@omniti.com (Wez Furlong)

On Oct 16, 2007, at 2:44 AM, sean finney wrote:

>
> i would suggest that anywhere where one is doing something with a  
> size or
> offset and not using the posix size_t/off_t types should get such  
> changes.
> and like i said, i don't see the motivation behind this extra step of
> returning the size in double form if it's bigger than LONG_MAX.

PHP's native integer type is long, how else are you going to relay  
numbers longer than a long back to the script without rewriting the  
engine to add additional integer types, which is a massive changeset?


> i don't think switching from long/int -> size_t is a problem in the  
> scope of
> function internal variables.  the only place where you need to  
> worry about
> this is in headers/structs/function declarations that are exported  
> to the
> API/ABI.

Or just bump our API number(s) and "not worry about it", since the  
module loading code will refuse to load an incompatible module.

PHP 5.3 is an ideal point to make this kind of change, as I've  
already stated.

--Wez.