rfc:calltimebyref

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:calltimebyref [2008/05/21 13:29] sfoxrfc:calltimebyref [2008/05/21 13:29] sfox
Line 33: Line 33:
  
 In some circumstances, on some platforms, passing values by reference can actually speed up your code. In most cases, though - and for all when it comes to large arrays - it carries a performance penalty. If you make use of by-ref for performance reasons on a given platform, that optimization will not be portable. In some circumstances, on some platforms, passing values by reference can actually speed up your code. In most cases, though - and for all when it comes to large arrays - it carries a performance penalty. If you make use of by-ref for performance reasons on a given platform, that optimization will not be portable.
 +
  
 ===== Future ===== ===== Future =====
  
-The directive is completely gone from CVS HEAD [3]. The effect of this originally was that a new-to-many ''E_STRICT'' would be thrown when values are returned by reference. However, it's been moved to ''E_DEPRECATED'' recently. In either case, it will no longer be possible to turn the warning off.+The directive is completely gone from CVS HEAD [3]. The effect of this originally was that a new-to-many ''E_STRICT'' would be thrown when values are passed by reference. However, it's been moved to ''E_DEPRECATED'' recently. In either case, it will no longer be possible to turn the warning off.
  
 ===== Proposal ===== ===== Proposal =====
rfc/calltimebyref.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1