PennMUSH Community

Changeset 1045

Show
Ignore:
Timestamp:
07/10/07 13:27:09 (1 year ago)
Author:
shawnw
Message:

#7401: help eval() clarification

Files:

Legend:

Unmodified
Added
Removed
Modified
Copied
Moved
  • 1.8.2/branches/devel/CHANGES.182

    r1029 r1045  
    1313 
    1414========================================================================== 
     15 
     16Version 1.8.2 patchlevel 7                       ????  ??, 2007 
     17 
     18Fixes: 
     19  * Clarified the behavior of eval() and get_eval() in help. 
     20    Suggested by  Talvo and Javelin. 
    1521 
    1622Version 1.8.2 patchlevel 6                       July 9, 2007 
  • 1.8.2/branches/devel/game/txt/hlp/pennfunc.hlp

    r917 r1045  
    11701170  get_eval(<object>/<attribute>) 
    11711171  
    1172   Eval() works the same way as xget(), except that it performs %-substitutions 
    1173   and function evaluation on the attribute before returning the value. eval() 
    1174   does not modify the stack (%0-%9), so the attribute being evaled sees the 
    1175   same values for them that the calling code does. Unless you need this behavior, 
    1176   it is better to use u() instead, which hides the caller's stack. 
     1172  Eval() works the same way as xget(), except that it performs 
     1173  %-substitutions and function evaluation on the attribute before 
     1174  returning the value. eval() changes the enactor (%#) to the object 
     1175  executing the eval (%!). It does not modify the stack (%0-%9), so 
     1176  the attribute being evaled sees the same values for them that the 
     1177  calling code does. Unless you need this behavior, it is better to 
     1178  use u() instead, which hides the caller's stack. 
    11771179 
    11781180    Example: