rfc:typecheckingstrictandweak

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:typecheckingstrictandweak [2010/06/08 15:48] – Added patch dmitryrfc:typecheckingstrictandweak [2010/06/09 14:17] – zeev
Line 96: Line 96:
  
 The auto-conversion would follow the current type juggeling rules. However in case of a cast that leads to data loss (like casting from '123abc' to an integer leading to 123 an E_FATAL notice would be raised. The auto-conversion would follow the current type juggeling rules. However in case of a cast that leads to data loss (like casting from '123abc' to an integer leading to 123 an E_FATAL notice would be raised.
- 
 ===== Patch ===== ===== Patch =====
  
-  * {{rfc:week_typechecking.diff.txt}}+  * {{:rfc:auto_converting_type_hinting.diff.txt}} - presently implements auto-converting type hinting without
  
 ===== Changelog ===== ===== Changelog =====
   * restructured to provide 3 options (two with current type juggeling rules and E_STRICT or E_FATAL on data loss conversion and one with new type juggeling rules and E_STRICT on data loss.   * restructured to provide 3 options (two with current type juggeling rules and E_STRICT or E_FATAL on data loss conversion and one with new type juggeling rules and E_STRICT on data loss.
rfc/typecheckingstrictandweak.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1

Page Tools