Hello, I wanted to take a moment to pick your brains on something I have been thinking about the last couple days.
While hacking and playing around with rosegarden, it's pretty obvious there are quite a few bugs that cause the application to crash -- NULL pointers etc etc (as Chris pointed out in a previous post). I am familiar with the purpose of the assert() macro, although have never really used it (mostly because I have never hacked on something as large as rosegarden). I have seen it used through peices of the code in base/. So, now onto some questions: Would the gui/ code benefit from things such as the assert() macro? If so, what would be an appropriate way of using it within the gui code? Would exceptions and exception handling be appropriate? What are the ramifications of using the -fno-exceptions compiler option? I am assuming this completely disabled exceptions, and I don't understand why you want to do that. I am trying to think of ways to minimize the chances of bugs being introduced into the code that the compiler cannot catch. I actually kind of like this sort of thing because I am not all that great at design. Any suggestions or comments are welcome. -- Levi Burton http://www.puresimplicity.net/~ldb/ ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ Rosegarden-devel mailing list [EMAIL PROTECTED] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
