John Anderson wrote: > How would you distinguish between chandler crashing when you exit and it > quiting normally? They are indistinguishable in the release version, > unless you happen to notice that your last change wasn't saved. In the > debug version you happen to get an assert.
You won't get an assert every time there is a crash. Some crashes are silent. > I wish we could get people more comfortable debugging wx because it's a > lot more productive than beating your head against the wall when you > can't figure why something in wx doesn't work like you expect. I find it > very liberating to be able to debug wx, and fixing a bug in wx instead > of adding a bunch of python hack to work around it feels good. If you find you are beating your head against the wall, then maybe. But I think most of the time it's faster to work around the issue in Python. > If we actually had good coverage testing the debug versions of Chandler > like they do for linux debug builds, then I wouldn't be so concerned. > But unfortuantely, we have very little testing with the debug builds. Unit tests run in debug and release mode. We'd need some extra boxes to run functional tests both in debug and release mode, and more time from someone to dedicate on tbox maintenance. -- Heikki Toivonen
signature.asc
Description: OpenPGP digital signature
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Dev" mailing list http://lists.osafoundation.org/mailman/listinfo/dev
