Re: Breakpoint woes

[John W. Eaton]

On 20-Apr-2009, John Swensen wrote:

| So I think I have an in-between solution that may fix all these  
| problems. I agree that we should be storing the entire filename in the  
| bp_table class. However, I find no reason why we should be storing the  
| octave_user_function pointer in a map with the function name as the  
| key.  Instead, I will only store the list of functions that have a  
| breakpoint. Then, when bp_table::do_get_breakpoint_list is called I  
| will check each function for breakpoints using get_user_code(),  
| getting the function body, and listing the breakpoints. If the number  
| of breakpoints comes back empty, then I will remove the full function  
| path and name from the list of functions.
| 
| Does this sound like a reasonable solution? I like this because the  
| bp_table becomes a much more passive class.

Yes, I think so.

Thanks,

jwe