On Fri, 8 Mar 2013 08:54:32 +1100 Lex Trotman <ele...@gmail.com> wrote:
> >> > Personally I prefer offensive programming: if something goes wrong, let > >> > it crash and burn, get a proper backtrace and fix it. > > I'm only complaining about the *deliberate* crash and burn policy you > seemed to be espousing. > > We should all try not to crash and burn in most reasonable circumstances. It's not like I'll crash the plugin because of invalid user input, errors in communication with gdb, incomplete/buggy gdb messages, or something like that - these are actually checked very strictly. What I don't do is to "defend" against programming errors in the plugin itself - for example, return 0 if the scope_array_get_element_size() emulations fails (that'll cause and endless loop). I used the Linux version for a month without a single crash or other bug, and think that it's reasonably safe (found a minor flaw, but we are in freeze now). There may be bugs, of course, and even crashes, but you should save your source files and compile them before debugging anyway. So you'd better Save All, especially under Windows. That's it. -- E-gards: Jimmy _______________________________________________ Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel
