On Sat, Aug 4, 2012 at 3:44 PM, Fernando Olivero <[email protected]>wrote:
> What about a Nautilus plugin, that allows browsing all the methods > that send #halt, #flag:,#log:? (the "development" messages). > > That's a great idea. In fact, I remember being sit at my desk in Douai and doing that with Guille.. Guille, do you remember? > Since finding all the halts, doesn't seem something that needs to be > performed all the time, an optional Nautilus plugin would suffice. > > > Fernando > > On Sat, Aug 4, 2012 at 3:02 PM, Sean P. DeNigris <[email protected]> > wrote: > > > > Mariano Martinez Peck wrote > >> > >>> Another thought, are there any plans for a "breakpoint" facility, so > that > >>> I don't dirty a package by only inserting 'self halt' to aid debugging. > >> it already exists. Right click on a method -> Add breakpoint > >> > > > > I, too would love to have the features you suggest. However, as it > stands, I > > would strongly advise against using breakpoints (someone definitely let > me > > know, maybe this is not still a problem in 2.0). In my experience, they > are > > incredibly buggy. Historically: > > * if you add a breakpoint in one tool, and try to disable it in another, > it > > may still be active; and who remembers what tool they enabled it in??? > > * there is very little feedback as to when a breakpoint is enabled > > - no icon in the browsers > > - the menu item was "toggle breakpoint" instead of dynamically "enable" > > vs. "disable" > > > > In all, I found it very confusing to figure out when a breakpoint was > > enabled, and how to disable. Of course, anyway, these are not > breakpoints as > > typically offered by an IDE, which can be attached to any statement, but > > only at the method level. > > > > Cheers, > > Sean > > > > > > > > -- > > View this message in context: > http://forum.world.st/self-halt-safety-net-tp4643012p4643070.html > > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > > > -- Mariano http://marianopeck.wordpress.com
