1. 24 Aug, 2007 1 commit
  2. 23 Aug, 2007 3 commits
  3. 30 Aug, 2007 2 commits
  4. 29 Aug, 2007 5 commits
  5. 30 Aug, 2007 2 commits
  6. 29 Aug, 2007 2 commits
  7. 24 Aug, 2007 1 commit
  8. 29 Aug, 2007 2 commits
  9. 28 Aug, 2007 1 commit
  10. 29 Aug, 2007 3 commits
  11. 28 Aug, 2007 4 commits
  12. 24 Aug, 2007 3 commits
  13. 28 Aug, 2007 3 commits
  14. 27 Aug, 2007 3 commits
    • mnislaih's avatar
      :stepover ---> :steplocal, :stepmodule · 3240dc3b
      mnislaih authored
       :stepover is declared a failed experiment. 
      :steplocal steps only on ticks contained in the current
      top level declaration. 
      :stepmodule steps only on ticks contained on the current
       module. 
      The current top level declaration and module are with
       respect to the breakpoint we are stopped on.
      
       The main reason for the failure of :stepover
      (apart from lacking a lexical call stack of course)
      is that it fails to detect when the expression being 
      evaluated is "complete", i.e. there are no ticks left in it.
      My assumption of the rightmost tick as the "last one",
      signaling that the expression is completely evaluated,
      is not true at all under laziness. 
      This assumption was key in the implementation of :stepover.
       
      3240dc3b
    • mnislaih's avatar
      Use a version of obtainTerm that takes a max depth bound · a27d12f0
      mnislaih authored
      when printing the contents of binding at a breakpoint
      a27d12f0
    • mnislaih's avatar
  15. 26 Aug, 2007 2 commits
  16. 24 Aug, 2007 1 commit
    • mnislaih's avatar
      A partial attempt to improve :stepover · 99794f66
      mnislaih authored
        
        With this patch, :stepover can effectively appear to step over recursive calls and 
        calls to locally bound functions (in a where clause).
        
        However, when we run out of ticks in the current expression, 
        the illusion vanishes and laziness brings us to the body of the last function 
        we "stepped over". 
        This is not desired at all, it is potentially very confusing.
        As a countermeasure, when this happens :stepover emits a warning
      
           "Warning: no more breakpoints in this function body, switching to :step"  
      99794f66
  17. 22 Aug, 2007 1 commit
  18. 28 Aug, 2007 1 commit