Re: Re: I quit.
| From: | Sven Drieling | Date: | Mon, 16 Feb 2015 18:45:22 +0000 |
| Subject: | Re: Re: I quit. | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-82873@lists.php.net to get a copy of this message | ||
Am Mon, 16 Feb 2015 18:00:41 +0200
schrieb Arvids Godjuks <arvids.godjuks@gmail.com>:
Hallo,
> Right now we need a breakthrough event - get type hints into the language
> at all. The most sensible thing to do it is to add basic type hints that
> work like the current conversion rules, maybe add some notices/warnings for
> some cases. Or adjust the conversion rules themselves in line with the new
> type hints.
Split a scalar typehints RFC in several smaller RFCs, problems, questions, discussions?
- Should PHP support scalar type hints?
- What are the advantages of the typehints for objects?
- What are the advantages of strict/weak types?
- Be aware of the type handling of internal functions:
- float silently converted to int
str_repeat ( string $input , int $multiplier )
echo str_repeat('a', 3.7);
- ...
- Validation of user submitted data in frameworks is already strict
type checking
- ...
tschuess
[|8:)