Req #72866 [ReO->Sus]: change default of $strict parameter of in_array()
Edit report at https://bugs.php.net/bug.php?id=72866&edit=1
ID: 72866
Updated by: stas@php.net
Reported by: imbibinebe at gmail dot com
Summary: change default of $strict parameter of in_array()
-Status: Re-Opened
+Status: Suspended
Type: Feature/Change Request
Package: *General Issues
Operating System: debian
PHP Version: 5.6Git-2016-08-17 (Git)
Block user comment: N
Private report: N
New Comment:
Thank you for your interest in PHP and for submitting a feature request. Please be aware that due to
the magnitude of change this request requires, it would be necessary to discuss it on PHP Internals
list (internals@lists.php.net) as an RFC. Please read the guide about creating RFCs here:
https://wiki.php.net/rfc/howto
If you haven't had experience with writing RFCs before, it is advised to seek guidance on the
Internals list (http://php.net/mailing-lists.php) and/or solicit help from one of the experienced
developers.
Please to not consider this comment as a negative view on the merits of your proposal - every
proposal which requires changes of certain magnitude, even the very successful and widely supported
ones, must be done through the RFC process. This helps make the process predictable, transparent and
accessible to all developers.
Previous Comments:
------------------------------------------------------------------------
[2016-08-17 19:06:50] ryosuke_i_628 at yahoo dot co dot jp
>> And at least, the final result resulting of my test is:
>> // 'string' == 0 -> bool(true)
>> should that be allright ? :)
Ooooops!!
String starts with non-numeric char is equivalent to zero.
My examples were completely wrong, sorry...
Needless to say this feature is very very confusing lol
------------------------------------------------------------------------
[2016-08-17 16:05:58] cmb@php.net
> I wished it as a feature request.
Actually, you had submitted it as feature request, but it sounded
more like a bug report to me.
> I think that having "bool $strict = FALSE" by default is very
> confusing (should be TRUE).
Okay, that might be possible without RFC, but at least some
discussion on internals@lists.php.net seems appropriate. Feel free
to write to the list.
------------------------------------------------------------------------
[2016-08-17 15:50:58] imbibinebe at gmail dot com
Sorry, Submitting this as a bug was my mistake. I wished it as a feature request.
I think that having "bool $strict = FALSE" by default is very confusing (should be TRUE).
At least the 2nd rule you gave me here is complex enough for not being the default behaviour in the
case of in_array function, I guess ...
Thank you all for your answers anyway.
------------------------------------------------------------------------
[2016-08-17 15:34:17] cmb@php.net
Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
http://www.php.net/manual/ and the instructions on how to
report
a bug at http://bugs.php.net/how-to-report.php
The manual states[1]:
| If you compare a number with a string or the comparison involves
| numerical strings, then each string is converted to a number and
| the comparison performed numerically.
And[2]:
| The value is given by the initial portion of the string. If the
| string starts with valid numeric data, this will be the value
| used. Otherwise, the value will be 0 (zero).
[1] <http://php.net/manual/en/language.operators.comparison.php>
[2] <http://php.net/manual/en/language.types.string.php#language.types.string.conversion>
------------------------------------------------------------------------
[2016-08-17 14:32:21] imbibinebe at gmail dot com
And at least, the final result resulting of my test is:
// 'string' == 0 -> bool(true)
should that be allright ? :)
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
https://bugs.php.net/bug.php?id=72866
--
Edit this bug report at https://bugs.php.net/bug.php?id=72866&edit=1
Thread (9 messages)