Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:75890
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain mabe.berlin from 80.237.132.171 cause and error)
Message-ID: <53CEA453.9050700@mabe.berlin>
Date: Tue, 22 Jul 2014 19:50:11 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: unsinged integer
From: php@mabe.berlin (Marc Bennewitz)

Hi all,

I like to create an RFC to add an unsinged integer type for the
following purposes:

- higher max value
  - DBs already allow UNSIGNED INT/BIGINT which is a farce to work with
in PHP
- better support pack/unpack unsigned integers from/to PHP using the
un/pack functions
- simplified right shift of unsinged integers because PHP "safes" the
sing bit on singed integers which leads to bugs or overcomplicated code
if you need that bit for others than a sign
- if a parameter type-hint or similar functionality will be implemented
this type will be very useful, too. Else it will be also useful to make
sure you have no negative integer by simply converting to it.

What do you think?
(Does it worth the expense for a RFC?)

Marc