Issue 7317 in pharo: [BUG]: Breakpoints clear on method change

Status: Accepted
Owner: [hidden email]
Labels: Type-Bug

New issue 7317 by [hidden email]: [BUG]: Breakpoints clear on method  
change
http://code.google.com/p/pharo/issues/detail?id=7317

Pharo2.0a
Latest update: #20483

1. In Nautilus (for example), in the context menu of the method list pane,  
select "Add breakpoint"
2. send the message, the breakpoint will be hit
3. alter and accept the method
4. send the message again, no breakpoint


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #1 on issue 7317 by [hidden email]: [BUG]: Breakpoints clear  
on method change
http://code.google.com/p/pharo/issues/detail?id=7317

 From the conversation in the original report (Issue 5896):

Benjamin.VanRyseghem:
The breakpoint thingy should be managed by the compiler or whatever, but  
not Nautilus :)
For that Nautilus only rely on something else.

marcus.denker:
breakpoints never worked really (very naive implementation).

They should be fixed, but not in 2.0

sven.van.caekenberghe:
Even if the functionality that we have now is incomplete, it is better than  
nothing.

It works, I use it a lot and I hate self halt because it makes methods  
dirty wrt monticello.




_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker