That would be better than the current situation, but, among other questions I'm probably not going to think of, it might be easy to decide how many debuggers are open when the error occurs, but how many are trying to open? Maybe a shared queue would suffice. Anyway, I get a vote, and it's in favor of notifiers; if there is further a preference to skip that step, that's fine by me.
Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: [email protected] Tel: (352) 273-6785 FAX: (352) 392-7029 >>> [email protected] 12/20/08 4:52 PM >>> So only open one and recognize eecursive UHE and do something clever. Opening an infinite # of any kind of window sucks. -david On Dec 20, 2008, at 2:58 PM, "Bill Schwab" <[email protected]> wrote: > Stef, > > Under ordinary circumstances, it's ok, but OA tried this and then > quickly decided it was a bad idea. Imagine a budding recursive > chain of > errors; the extra load of opening the debugger can prevent a rescue > that > might be possible given a lightweight notifier. > > Bill > > > > > > Wilhelm K. Schwab, Ph.D. > University of Florida > Department of Anesthesiology > PO Box 100254 > Gainesville, FL 32610-0254 > > Email: [email protected] > Tel: (352) 273-6785 > FAX: (352) 392-7029 > >>>> [email protected] 12/20/08 2:37 PM >>> > ahh now I understand because I'm often working on pharo core and I > could not really understand > what was the problem. > > Now indeed what is wrong with getting just the debugger? assuming the > same error is raised? > stef > On Dec 20, 2008, at 6:51 PM, Lukas Renggli wrote: > >> On Sat, Dec 20, 2008 at 6:45 PM, Adrian Lienhard <[email protected]> >> wrote: >>> I don't quite understand. When I do "1 foo" I get a notifier window >>> (the small one) and not the full debugger. >> >> I guess Bill is using the Dev-Image of Damien with OB-Tools loaded. >> >> Lukas >> >> -- >> Lukas Renggli >> http://www.lukas-renggli.ch >> >> _______________________________________________ >> Pharo-project mailing list >> [email protected] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
