Hi everyone,
There is one unresolved issue with the current patch that the RFC
doesn't address, so I'll ask about it here.
As part of supporting exponent notation in all remaining integer
operations (casts, operators), I would like to have intval() support it,
to match the `(int)` cast.
> -Original Message-
> From: Andrea Faulds [mailto:a...@ajf.me]
> Sent: Tuesday, January 26, 2016 11:36 PM
> To: internals@lists.php.net
> Subject: [PHP-DEV] Re: [RFC] Warn about invalid strings in arithmetic (moving
> back todiscussion)
>
> ...I proof-read my emai
On 27/01/16 01:54, Levi Morrison wrote:
> I personally consider the new changes with fractional and scientific
> notation strings and integer operators to be the more important
> change. Thanks to everyone who identified and fixed this
> inconsistency.
>
> Does anyone have any good ideas on how
Hi Levi,
Levi Morrison wrote:
I personally consider the new changes with fractional and scientific
notation strings and integer operators to be the more important
change. Thanks to everyone who identified and fixed this
inconsistency.
Does anyone have any good ideas on how to prevent strtol
...I proof-read my email, but I forgot the most important thing. The link!
https://wiki.php.net/rfc/invalid_strings_in_arithmetic
Sorry.
Andrea Faulds wrote:
Good evening,
I had opened the vote for this RFC, but then I was reminded by a
discussion in the pull request about a particular
I personally consider the new changes with fractional and scientific
notation strings and integer operators to be the more important
change. Thanks to everyone who identified and fixed this
inconsistency.
Does anyone have any good ideas on how to prevent strtol and strtod
from being re-introduced
On Tue, Jan 26, 2016 at 7:54 PM, Levi Morrison wrote:
> I personally consider the new changes with fractional and scientific
> notation strings and integer operators to be the more important
> change. Thanks to everyone who identified and fixed this
> inconsistency.
>
Seconded,