> On May 11, 2015, at 9:05 PM, Sara Golemon wrote:
>
>> On Mon, May 11, 2015 at 5:12 PM, Matt Wilmas wrote:
>> - Original Message -
>> From: "Stanislav Malyshev"
>> Sent: Monday, May 11, 2015
>>
argument. I'd like to propose making the order of evaluation defined
by splitting
Hi!
> - is_digits() and digits type for digits only inputs(integer like string)
> - is_numeric() and numeric type for float like string
This is not what types are in PHP, and not what they should be, IMO. If
you want to assign arbitrary checks to a variable, I would suggest using
a class with a
On Mon, May 11, 2015 at 5:12 PM, Matt Wilmas wrote:
> - Original Message -
> From: "Stanislav Malyshev"
> Sent: Monday, May 11, 2015
>
>>> argument. I'd like to propose making the order of evaluation defined
>>> by splitting this into separate statements:
>>
>> What is the purpose of this
You know, given how worried you seem to be about this issue, could you
booby trap your so that if the developers use the wrong type (int vs.
string) the program throws fatal errors with nasty error messages that
explain how much trouble the developer is in at the userland code level?
While I like
Hi all,
Firstly, I don't intend this for PHP 7.0 strictly.
PHP is made for Web. It means PHP is made for interacting other
systems/data. Currently, we only have "int" and "float" strictly bounded
to native "unsigned int" and "IEEE 754 double". This causes problems
for interacting other systems/da
Hi!
- Original Message -
From: "Stanislav Malyshev"
Sent: Monday, May 11, 2015
Hi!
argument. I'd like to propose making the order of evaluation defined
by splitting this into separate statements:
What is the purpose of this? I.e. why is it important that these notices
would be prod
Hi!
> argument. I'd like to propose making the order of evaluation defined
> by splitting this into separate statements:
What is the purpose of this? I.e. why is it important that these notices
would be produced in certain order?
--
Stas Malyshev
smalys...@gmail.com
--
PHP Internals - PHP Runt
http://3v4l.org/uVNIS
Prior to PHP 5.1 (and the introduction of compiled variables), the
following code would output warnings for the undefined variables in
the order they were used:
echo $x . $y . $z;
However, with the introduction of CVs, we wind up getting the warning
for $y, then $x, and fin
On May 11, 2015 6:01 PM, "Arvids Godjuks" wrote:
>
> пн, 11 Май 2015, 10:21, Yasuo Ohgaki :
>
> Hi all,
>
>
> I've never wrote my blog in English, but I wrote one because peice by
piece
> discussion is not going to anywhere.
>
> http://blog.ohgaki.net/dont-use-php7-type-hint-for-external-data
>
>
пн, 11 Май 2015, 10:21, Yasuo Ohgaki :
Hi all,
I've never wrote my blog in English, but I wrote one because peice by piece
discussion is not going to anywhere.
http://blog.ohgaki.net/dont-use-php7-type-hint-for-external-data
How many of you think current scalar type hint is useful enough to in
hi Levi!
On Mon, May 11, 2015 at 3:01 AM, Levi Morrison wrote:
>> Again, this is a C11 feature. It is supported by clang, gcc and MSVC.
>
> To clarify this a bit: they permit anonymous unions in C89 and C99
> code (meaning you do not need to pass flags like -std=c11 to enable
> it).
https://gith
Hi,
On Sun, May 10, 2015 22:01, Levi Morrison wrote:
>> Again, this is a C11 feature. It is supported by clang, gcc and MSVC.
>>
>
> To clarify this a bit: they permit anonymous unions in C89 and C99
> code (meaning you do not need to pass flags like -std=c11 to enable it).
>
particularly regardin
Hi all,
On Wed, Apr 29, 2015 at 8:50 AM, Yasuo Ohgaki wrote:
> External data can have any form of numbers.
> Current PHP can handle them as "string". However PHP7's type hint cannot
> handle numeric data well because it only has "int" and "float" hints.
>
> http://3v4l.org/6J0bZ
>
> There are ca
13 matches
Mail list logo
