btmux-0.6-rc4/doc/
btmux-0.6-rc4/event/
btmux-0.6-rc4/game/
btmux-0.6-rc4/game/maps/
btmux-0.6-rc4/game/mechs/
btmux-0.6-rc4/game/text/help/
btmux-0.6-rc4/game/text/help/cat_faction/
btmux-0.6-rc4/game/text/help/cat_inform/
btmux-0.6-rc4/game/text/help/cat_misc/
btmux-0.6-rc4/game/text/help/cat_mux/
btmux-0.6-rc4/game/text/help/cat_mux/cat_commands/
btmux-0.6-rc4/game/text/help/cat_mux/cat_functions/
btmux-0.6-rc4/game/text/help/cat_templates/
btmux-0.6-rc4/game/text/wizhelp/
btmux-0.6-rc4/include/
btmux-0.6-rc4/misc/
btmux-0.6-rc4/python/
btmux-0.6-rc4/src/hcode/btech/
btmux-0.6-rc4/tree/
& eval()
 
  Syntax: eval(<object>,<attribute>)
  Syntax: eval(<string>)
 
  The first form of the eval function works exactly like the 
  get_eval() function, but takes the object and attribute in two 
  seperate arguments instead of an obj/attr pair. It is mainly used 
  for compatibility with PennMUSH 1.50. 
  
  The second form simply evaluates <string>. This is normally done 
  when a function is called, however, it is useful in evaluating %q 
  and %v substitutions.
 
  See Also: get_eval(), get(), xget()