anchor.diff:  ;; it is going to have to look inside the lexical scope of the 
   ;; closure...this sounds ugly.
   
  -;; time-buffer relative real time since last call
  -;; time-cache relative time since made(/last reset?)
  +;; time-buffer - converts absolute time to relative time
  +;; time-cache - converts relative time to absolute time
   ;;
   ;; both of these have time sources.
   ;; time-cache can be made using time-buffer so may not be equal
  
positive.code: ;; multiple threads).
  
  ;; But we still have the problem of.'what if a lambda does get
  ;; passed *expired?* and DOESNT crash, we have undefined 
  ;; behaviour.
  
  ;; how about conditionals?...been chatting and could be good
  
negative.code: (defun expired (temporal-lambda)
    (funcall temporal-lambda :*expired?*))
  
  ;; look into variable capture as is not currently portable for 
  ;; regular lambdas as passing :*expired?* will crash them.
  
  (defvar *expired?* nil)
  
  