rfc:introduce-type-affinity
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
| rfc:introduce-type-affinity [2015/03/16 22:15] – yohgaki | rfc:introduce-type-affinity [2017/09/22 13:28] – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 29: | Line 29: | ||
| * Detect possible data type without definition/ | * Detect possible data type without definition/ | ||
| - | * Have INI option for type affinity conversion | + | * Have INI option for type affinity conversion |
| * 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/ | * Provide data type definition/ | ||
| - | * Apply type affinity function and convert | + | * Apply type affinity function and convert |
| * If there is conversion error, it may raise error | * If there is conversion error, it may raise error | ||
| Line 40: | Line 40: | ||
| Introduce type affinity conversion function: | Introduce type affinity conversion function: | ||
| - | * void type_affinitize(mixed $input [, array $definition ]); | + | * void type_affinitize(mixed |
| * void type_affinitize_input(string $input=" | * void type_affinitize_input(string $input=" | ||
rfc/introduce-type-affinity.txt · Last modified: 2021/03/27 14:50 by ilutov