what happened with gds breakpoints?

[Andy Wingo]

Hi Neil,

Why did you remove GDS breakpoints? The idea sounded nice:

    While they are an important piece of infrastructure, and directly
    usable in some scenarios, traps are still too low level to meet some
    of the requirements of interactive development.

    A common scenario is that a newly written procedure is not working
    properly, and so you'd like to be able to step or trace through its
    code to find out why.  Ideally this should be possible from the IDE
    and without having to modify the source code.  There are two problems
    with using traps directly in this scenario.

    @enumerate
    @item
    They are too detailed: constructing and installing a trap requires you
    to say what kind of trap you want and to specify fairly low level
    options for it, whereas what you really want is just to say ``break
    here using the most efficient means possible.''

    @item
    The most efficient kinds of trap --- that is, @code{<procedure-trap>}
    and @code{<source-trap>} --- can only be specified and installed
    @emph{after} the code that they refer to has been loaded. 

Just wondering.

Andy  
-- 
http://wingolog.org/