On Jan 17, 2015 7:22 PM, "Andrea Faulds" wrote:
>
> Hey Pierre,
>
> > On 17 Jan 2015, at 05:56, Pierre Joye wrote:
> >
> > It looks to me like yet another can of worms (how do you deal with
> > conversions, mixed operations, etc. it adds a lot of special cases)
> > with little benefits.
>
> The c
Hey Pierre,
> On 17 Jan 2015, at 05:56, Pierre Joye wrote:
>
> It looks to me like yet another can of worms (how do you deal with
> conversions, mixed operations, etc. it adds a lot of special cases)
> with little benefits.
The conversions are trivial and there are no operations to implement. T
On Sat, Jan 17, 2015 at 4:32 AM, Andrea Faulds wrote:
> Hi Marc,
>
> This is an unusual follow-up from me.
>
> Particularly on 32-bit systems, it would be useful to have a ‘u’
> zend_parse_parameters specifier for an unsigned integer. Unfortunately,
> again, I don’t think native unsigned integer
Hi Marc,
This is an unusual follow-up from me.
Particularly on 32-bit systems, it would be useful to have a ‘u’
zend_parse_parameters specifier for an unsigned integer. Unfortunately, again,
I don’t think native unsigned integers (IS_ULONG) will get into PHP. But it
looks like the bigint RFC p
On 22 Jul 2014, at 21:21, Rowan Collins wrote:
> More seriously, UnsignedInt might go nicely alongside Andrea's BigInts…
Bigints kinda remove the need for unsigned ints as you’d be able to use big
signed integers of any size. I also really don’t want unsigned int because it
makes integer sema
On 22 Jul 2014, at 18:50, Marc Bennewitz wrote:
> 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/
ups (typo + copy past error)
It's not my day today!
On 22.07.2014 22:21, Rowan Collins wrote:
> On 22/07/2014 20:55, Marc Bennewitz wrote:
>> I like to create an RFC to add an unsinged integer type
>
> +1 for not turning the iron up too high when doing your maths!
>
> [https://en.wiktionary.org
On Tue, Jul 22, 2014 at 9:55 PM, Marc Bennewitz
wrote:
> 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 unsig
On 22/07/2014 20:55, Marc Bennewitz wrote:
I like to create an RFC to add an unsinged integer type
+1 for not turning the iron up too high when doing your maths!
[https://en.wiktionary.org/wiki/singe]
Sorry, it's a common typo, but it made me chuckle that you used it in
both the subject and
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 s
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 s
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 s
12 matches
Mail list logo
