rfc:introduce-type-affinity

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
rfc:introduce-type-affinity [2015/03/16 22:15] yohgakirfc:introduce-type-affinity [2021/03/27 14:50] (current) – Move to inactive ilutov
Line 3: Line 3:
   * Date: 2015-03-16   * Date: 2015-03-16
   * Author: Yasuo Ohgaki <yohgaki@ohgaki.net>   * Author: Yasuo Ohgaki <yohgaki@ohgaki.net>
-  * Status: Draft+  * Status: Inactive
   * First Published at: http://wiki.php.net/rfc/introduce-type-affinity   * First Published at: http://wiki.php.net/rfc/introduce-type-affinity
  
Line 29: Line 29:
  
   * Detect possible data type without definition/hint   * Detect possible data type without definition/hint
-  * Have INI option for type affinity conversion+  * Have INI option for type affinity conversion (When "On", affinity conversion is done always for $_GET/$_POST/etc)
   * Data is stored with native data type   * Data is stored with native data type
   * Conversion will never raise error   * Conversion will never raise error
  
   * Provide data type definition/hint prior to the conversion   * Provide data type definition/hint prior to the conversion
-  * Apply type affinity function and convert+  * Apply type affinity function and convert (User must write code unlike previous one)
   * If there is conversion error, it may raise error   * If there is conversion error, it may raise error
  
rfc/introduce-type-affinity.1426544142.txt.gz · Last modified: 2017/09/22 13:28 (external edit)