/** @addtogroup XBT_API
*
+ * The XBT functionalities fall into several categories:
+ * - Portability support.
+ * - \ref XBT_syscall
* - Grounding features
* - \ref XBT_log
* - \ref XBT_error
* - \ref XBT_fifo
* - \ref XBT_swag
* - \ref XBT_heap
- * - Portability support. The targeted audiance of this portability support
- * is merly the programming environments (\ref MSG_API, \ref GRAS_API and
- * \ref SMPI_API), not the user code which should get its portability from
- * the used programming environment.
- * - \ref XBT_context
*
* @{
*/
+
+/* *************** *
+ * * PORTABILITY * *
+ * *************** */
+
+ /** @defgroup XBT_syscall Malloc and friends
+ * @brief malloc and associated functions, killing the program on error
+ */
+
/* ************* *
* * GROUNDING * *
* ************* */
/** \addtogroup XBT_fifo
\ingroup XBT_API */
-/** \addtogroup XBT_swag
- \ingroup XBT_API */
+
+ /** @defgroup XBT_swag A O(1) set datatype
+ * @brief a O(1) set based on linked lists
+ */
+
/** \addtogroup XBT_heap
\ingroup XBT_API */
-/* *************** *
- * * PORTABILITY * *
- * *************** */
+/* ************************* *
+ * * PORTABILITY-INTERNALS * *
+ * ************************* */
/** \defgroup XBT_context Portable context implementation
* \brief Contexts are a higher level system than <tt>setjump/longjmp</tt>
* implementation of the serveral programmation environment of the
* SimGrid toolkit (nammely, \ref MSG_API, \ref GRAS_API and \ref SMPI_API).
*
- * You should use those mecanism instead.
+ * You should use those mechanism instead.
*/