Use statically-allocated thread private data

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

diff --git a/libchimara/timer.c b/libchimara/timer.c
index 400f5062f1d6dd86fc764daf8399f8f8834af377..cebe6fe31c646820fdc02a2bc65dba6e0b0a3e2c 100644 (file)
--- a/libchimara/timer.c
+++ b/libchimara/timer.c
@@ -1,6 +1,6 @@
 #include "timer.h"
 
-extern GPrivate *glk_data_key;
+extern GPrivate glk_data_key;
 
 /**
  * glk_request_timer_events:
@@ -35,7 +35,7 @@ extern GPrivate *glk_data_key;
  *  This prevents the user from being locked out by overly enthusiastic timer 
  *  events. Unfortunately, it also means that your timer can be locked out on 
  *  slower machines, if the player pounds too enthusiastically on the keyboard. 
- *  Sorry. If you want a real-time operating system, talk to Wind River.
+ *  Sorry.
  * </para></note>
  *
  * <note><para>
@@ -46,8 +46,8 @@ extern GPrivate *glk_data_key;
 void
 glk_request_timer_events(glui32 millisecs)
 {
-       ChimaraGlkPrivate *glk_data = g_private_get(glk_data_key);
-       
+       ChimaraGlkPrivate *glk_data = g_private_get(&glk_data_key);
+
        // Stop any existing timer
        if(glk_data->timer_id != 0) {
                g_source_remove(glk_data->timer_id);