rfc:typecheckingweak

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
rfc:typecheckingweak [2009/07/12 13:52] – Some fixes and additions. zeevrfc:typecheckingweak [2009/07/12 15:11] – zeev
Line 88: Line 88:
  
 //as-is// - designates that the value is passed as-is, without conversion //as-is// - designates that the value is passed as-is, without conversion
 +
 +**Note:**  'scalar' and 'array' type hints remain unchanged - an array typed argument will only accept arrays, and will otherwise fail;  A scalar typed argument will accept any kind of scalar argument, but will fail on objects and arrays.
  
 In a nutshell, the conversion logic is quite similar to the one employed by internal functions, with one key difference - it is designed to fail in case of a conversion that is unlikely to 'make sense'.  Specifically, it breaks away from PHP's internal function behavior in two key places: In a nutshell, the conversion logic is quite similar to the one employed by internal functions, with one key difference - it is designed to fail in case of a conversion that is unlikely to 'make sense'.  Specifically, it breaks away from PHP's internal function behavior in two key places:
rfc/typecheckingweak.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1

Page Tools