From: David B. <dav...@gm...> - 2010-12-20 03:43:58
|
Hi, >> Debugging Messages - Sorry, I couldn't understand the debugging system. >> (However, it does handle errors, and pretty well, at that) > > I think it would be a really good idea to incorporate the debugging > system from the start. Sorry, sent the message before I finished what I was trying to say. The run-time debugging output involves a couple of macros defined in t4k_common, plus a group of bit flags (can be combined with '|') that determine what part of tuxmath should produce output. Just look at mathcards.c for examples of how to use DEBUGMSG and DEBUGCODE. The needed includes are #include "globals.h" and #include <t4k_common.h>. >> Generating Questions From Wrong Answers If you are using a doubly-linked list, it is pretty easy to move the nodes into a new list rather than deleting them. >> Also, it's completely in the (newly planned) coding style for TuxMath. Actually, I prefer corresponding braces to be vertically aligned in the same column, but I'm not a zealot about it. What do other tuxmath devs think? If most people like the opening brace at the end of the function signature, I'm OK with it, but let's keep the changes to a minimum unless there is really a consensus. However, I think we all agree that my two-space indenting can be changed to four spaces. Anyway, it looks like you've put a lot of work into it so far. It looks like you are keeping the same basic idea of a doubly-linked list to hold the questions. Best, David |