The messages involved in this example do use structures as payload,
so we have to declare it to GRAS. Hopefully, this can be done easily by enclosing
- the structure declaration within a GRAS_DEFINE macro call. It will then copy this
+ the structure declaration within a \ref GRAS_DEFINE_TYPE macro call. It will then copy this
declaration into an hidden string variable, which can be automatically parsed at
run time. Of course, the declaration is also copied unmodified by this macro, so that it
gets parsed by the compiler also.
imply. If you want to use it yourself, you'd better use the exact right syntax, which is
detailed in the \ref GRAS_dd section.
- \skip GRAS_DEFINE
+ \skip GRAS_DEFINE_TYPE
\until matrix_t
\subsection GRAS_ex_mmrpc_msgregister 1.c) Register the messages
This function, called by both the client and the server is in charge of
declaring the existing messages to GRAS. Note the use of the \ref gras_datadesc_by_symbol
- function to parse and retrieve the structure declaration which were passed to \ref GRAS_DEFINE
+ function to parse and retrieve the structure declaration which were passed to \ref GRAS_DEFINE_TYPE
above.
The datatype description builded that way can then be used to build an array datatype or
