On Thu, 07 Mar 2013 11:37:50 -0800 Matthew Brush mbrush@codebrainz.ca wrote:
Personally I prefer offensive programming: if something goes wrong, let it crash and burn, get a proper backtrace and fix it.
Note to self: don't use Scope plugin until all files are saved :)
You should save and compile the source files at least. Otherwise, debugging may be confusing. ;)
On Fri, 8 Mar 2013 06:44:15 +1100 Lex Trotman elextr@gmail.com wrote:
In which case this plugin must be removed from G-P until you have a reasonable assurance it won't bring Geany down. You may prefer crash and burn, but you should not impose that on innocent G-P users.
All sorts of invalid glib/gtk calls can bring Geany down without any messages, the g_return_*() checks in the libraries are by no means complete. So, it depends on the exact value of "reasonable".
The drawbacks of defensive programming are that bugs tend to stay unfixed, sunce they just emit a message in ~/.xsession-errors, and nobody notices/cares (I have several of those since forever); the clumsier way to get a proper stack trace; and the unpredictable caller behaviour when a function is not executed because of a g_return_*() - it may crash in some random place, and then you will receive an error report - but a wrong one (if the log messages are missing), or less helpful (with them included).