rfc:reflectionparameter.typehint
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision |
rfc:reflectionparameter.typehint [2014/05/30 16:28] – Formatting improvements. levim | rfc:reflectionparameter.typehint [2014/05/30 16:34] – Improved Introduction. levim |
---|
===== Proposal ===== | ===== Proposal ===== |
| |
This RFC proposes a class to represent type information; it also adds methods to ReflectionParameter to utilize this information: <php>ReflectionParameter::hasTypeAnnotation()</php> and <php>ReflectionParameter::getTypeAnnotation()</php>. Additionally it adds an explicit ''%%__toString%%'' method to make parsing function/method signatures and replicating them for mocking frameworks simpler. | This RFC proposes a new class ''ReflectionTypeAnnotation'' to represent type information; currently this information is contained on the ''ReflectionParameter'' class. This RFC adds methods to ''ReflectionParameter'' to use this new class: <php>ReflectionParameter::hasTypeAnnotation()</php> and <php>ReflectionParameter::getTypeAnnotation()</php>. If the Return Type RFC is accepted it will then it will also use this new ''ReflectionTypeAnnotation'' class. |
| |
Current mocking frameworks have to cast the ReflectionParameter to a string, then text parse that string to retrieve the information. | The class ''ReflectionTypeAnnotation'' also has ''%%__toString%%'' method to make parsing function/method signatures and replicating them for mocking frameworks simpler; current mocking frameworks have to cast the ReflectionParameter to a string, then text parse that string to retrieve the information. |
| |
===== Proposed PHP Version(s) ===== | ===== Proposed PHP Version(s) ===== |
rfc/reflectionparameter.typehint.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1