gras_init(&argc,argv);
- globals=gras_userdata_new(server_data_t*);
+ globals=gras_userdata_new(server_data_t);
globals->killed=0;
gras_msgtype_declare("hello", NULL);
\skip userdata_new
\until userdata_new
+BEWARE, the gras_userdata_new expects the pointed type, not the
+pointer type. As you can see, in our example, you should pass
+server_data_t to the macro, even if the global variable is later
+defined as being of type server_data_t*.
+
Once you declared a global that way, retriving this (for example in a
callback) is really easy:
\dontinclude 05-globals.c
* and use \ref gras_userdata_set yourself), and \ref gras_userdata_get to
* retrieve a reference to it.
*
+ *
* For more info on this, you may want to check the relevant lesson of the GRAS tutorial:
* \ref GRAS_tut_tour_globals
*/
*/
XBT_PUBLIC(void) gras_userdata_set(void *ud);
-/** \brief Malloc and set the data associated with the current process. */
+/** \brief Malloc and set the data associated with the current process.
+ *
+ * @warnug gras_userdata_new() expects the pointed type, not the
+ * pointer type. We know it'a a bit troublesome, but it seems like
+ * the only solution since this macro has to compute the size to
+ * malloc and should thus know the pointed type.
+ *
+ * You'll find an example in the tutorial: \ref GRAS_tut_tour_globals
+ */
#define gras_userdata_new(type) (gras_userdata_set(xbt_new0(type,1)),gras_userdata_get())
/* @} */