Updated documentation to match API 0.7.2

[projects/chimara/chimara.git] / libchimara / glk.c

diff --git a/libchimara/glk.c b/libchimara/glk.c
index 81d3603fba2c613a49b3fb32dd9e48260ab5d7e0..f5df12ee4cc80c7fd88dd055bb11f91f52f6085f 100644 (file)
--- a/libchimara/glk.c
+++ b/libchimara/glk.c
@@ -100,8 +100,10 @@ glk_exit(void)
  * all. So you can call it often.
  *
  * <note><para>
- *   In a virtual machine interpreter, once per opcode is appropriate. In a
- *   program with lots of computation, pick a comparable rate.
+ *   In a virtual machine interpreter, once per opcode is appropriate. A more
+ *   parsimonious approach would be once per branch and function call opcode;
+ *   this guarantees it will be called inside loops. In a program with lots of
+ *   computation, pick a comparable rate.
  * </para></note>
  * 
  * glk_tick() does not try to update the screen, or check for player input, or