X-Git-Url: https://git.stderr.nl/gitweb?a=blobdiff_plain;f=libchimara%2Fglk.c;h=f5df12ee4cc80c7fd88dd055bb11f91f52f6085f;hb=02c13aec1755ce0397011d502a92a80d1f69ea43;hp=81d3603fba2c613a49b3fb32dd9e48260ab5d7e0;hpb=43b334356e9e0003589d506ae74a8c85e5b9349d;p=projects%2Fchimara%2Fchimara.git

diff --git a/libchimara/glk.c b/libchimara/glk.c
index 81d3603..f5df12e 100644
--- 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