rfc:typecheckingstrictonly
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
rfc:typecheckingstrictonly [2009/07/03 20:45] – Simple placeholder pbiggar | rfc:typecheckingstrictonly [2017/09/22 13:28] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Request for Comments: | + | ====== Request for Comments: |
- | * Version: | + | * Version: |
- | * Date: | + | * Date: October 22, 2009 |
- | * Author: | + | * Author: |
- | * Status: | + | * Status: |
* First Published at: http:// | * First Published at: http:// | ||
+ | The idea is that certain applications and/or use cases could benefit from the ability to specify the specific types that functions and methods accept as parameters. The benefits of this approach is the improved code clarity and more detailed code interrogation via reflection for the purposes of WSDL and automatic comment generation. There are also security benefits of effectively being able to perform strict type checking around input parameters. | ||
- | A placeholder | + | The patch is available here: http:// |
+ | The test cases around the functionality are available | ||
- | http://news.php.net/ | + | The implemented functionality does " |
+ | The supported type hints are as follows: (int/ | ||
+ | The " | ||
+ | The patch also introduces additional methods into reflection, to simplify interrogation of the code. | ||
+ | |||
+ | ReflectionParameter:: | ||
+ | |||
+ | ReflectionParameter:: | ||
+ | |||
+ | ReflectionParameter:: | ||
+ | |||
+ | ReflectionParameter:: | ||
+ | |||
+ | ReflectionParameter:: | ||
+ | |||
+ | ReflectionParameter:: | ||
+ | |||
+ | ReflectionParameter:: |
rfc/typecheckingstrictonly.1246653930.txt.gz · Last modified: 2017/09/22 13:28 (external edit)