rfc:comparison_inconsistency

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
rfc:comparison_inconsistency [2014/01/08 01:56] yohgakirfc:comparison_inconsistency [2014/01/11 02:53] yohgaki
Line 2: Line 2:
 ====== PHP RFC: Existing comparison and conversion behaviors to discuss/document  ====== ====== PHP RFC: Existing comparison and conversion behaviors to discuss/document  ======
   * Version: 0.1   * Version: 0.1
-  * Date: 2013-10-31+  * Date: 2014-01-08
   * Author: Yasuo Ohgaki <yohgaki@php.net>   * Author: Yasuo Ohgaki <yohgaki@php.net>
   * Status: Draft (or Under Discussion or Accepted or Declined)   * Status: Draft (or Under Discussion or Accepted or Declined)
Line 181: Line 181:
 ==== Object Array conversion of numeric property/index ==== ==== Object Array conversion of numeric property/index ====
  
 +Object/Array cast looses accessibility of numeric property/element.
 https://bugs.php.net/bug.php?id=66173 https://bugs.php.net/bug.php?id=66173
  
Line 206: Line 207:
  
  
-==== Function/Method ====+===== Function/Method =====
  
-=== is_numeric ===+==== is_numeric ====
  
 https://bugs.php.net/bug.php?id=66399 https://bugs.php.net/bug.php?id=66399
  
  
-=== base_convert ====+==== base_convert ====
  
 https://wiki.php.net/rfc/base-convert https://wiki.php.net/rfc/base-convert
  
  
-=== min() function ===+==== min() function ====
  
 https://bugs.php.net/bug.php?id=53104 https://bugs.php.net/bug.php?id=53104
Line 224: Line 225:
 This is not a bug. If one of operand is BOOL(or NULL), both operands are converted to BOOL and evaluated as BOOL. It may be good idea that document this behavior in min() manual. This is not a bug. If one of operand is BOOL(or NULL), both operands are converted to BOOL and evaluated as BOOL. It may be good idea that document this behavior in min() manual.
  
-=== Return value of wrong internal function/method parameters ===+==== Return value of wrong internal function/method parameters ====
  
 If not all, almost all functions return NULL when required function parameter is missing or wrong type. However, almost all functions return FALSE when they have errors. If not all, almost all functions return NULL when required function parameter is missing or wrong type. However, almost all functions return FALSE when they have errors.
Line 263: Line 264:
 Bug reports are not verified carefully. Removing wrong one, adding proper one is appreciated. Bug reports are not verified carefully. Removing wrong one, adding proper one is appreciated.
  
-== Developer Guideline ==+===== Developer Guideline =====
  
   * Internal function/method should raise error(or exception) for invalid parameters. (parse parameters function does this)   * Internal function/method should raise error(or exception) for invalid parameters. (parse parameters function does this)
Line 269: Line 270:
   * Internal function/method is better to return FALSE for other errors.   * Internal function/method is better to return FALSE for other errors.
  
-== User Guideline ==+===== User Guideline =====
  
   * User should not rely return value only for failure condition, but should rely error/exception handler for failure also.   * User should not rely return value only for failure condition, but should rely error/exception handler for failure also.