Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:80672
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain ajf.me designates 192.64.116.207 as permitted sender)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
In-Reply-To: <53CEC194.5090307@marc-bennewitz.de>
Date: Sat, 17 Jan 2015 03:32:49 +0000
Cc: internals@lists.php.net
Content-Transfer-Encoding: quoted-printable
Message-ID: <2DD279B4-E872-4FDA-9FDC-12770D4BF052@ajf.me>
References: <53CEC194.5090307@marc-bennewitz.de>
To: Marc Bennewitz <php@marc-bennewitz.de>
Subject: Re: [PHP-DEV] unsinged integer
From: ajf@ajf.me (Andrea Faulds)

Hi Marc,

This is an unusual follow-up from me.

Particularly on 32-bit systems, it would be useful to have a =91u=92 =
zend_parse_parameters specifier for an unsigned integer. Unfortunately, =
again, I don=92t think native unsigned integers (IS_ULONG) will get into =
PHP. But it looks like the bigint RFC probably will, and here=92s the =
opportunity.

With the bigint RFC, we could add a =91u=92 specifier. You=92d get a =
native ulong (zpp would convert from long or bigint), and could easily =
produce a long/bigint from your ulong if you need to return one (add =
RETURN_ULONG which implicitly converts?).

Now, it=92s not as fast as a native IS_ULONG type would be, but we could =
still do things like properly support file sizes in the 2GB-4GB range on =
32-bit, at least. :)

What do you think?

--
Andrea Faulds
http://ajf.me/