-/** \defgroup MSG_JAVA jMSG
- \ingroup MSG_API
- \brief Java bindings to MSG (\ref MSG_API)
-
- \htmlonly <!--
- DOXYGEN_NAVBAR_LABEL="JAVA bindings"
- DOXYGEN_NAVBAR_CHILD "Simulation functions"=classsimgrid_1_1msg_1_1Msg.html
- DOXYGEN_NAVBAR_CHILD "Host"=classsimgrid_1_1msg_1_1Host.html
- DOXYGEN_NAVBAR_CHILD "Process"=classsimgrid_1_1msg_1_1Process.html
- DOXYGEN_NAVBAR_CHILD "Task"=classsimgrid_1_1msg_1_1Task.html
- DOXYGEN_NAVBAR_CHILD "MsgException"=classsimgrid_1_1msg_1_1MsgException.html
- --> \endhtmlonly
-
- MSG was the first distributed programming environment provided within
- SimGrid. While almost realistic, it remains quite simple (simplistic?).
- This describes the Java bindings to this interface.
-
- \section jMSG_who Who should use this (and who shouldn't)
-
- You should use MSG if you want to study some heuristics for a
- given problem you don't really want to implement. If you want to
- use the Java programming language, your are in the right
- section. To use the C interface, please refer to \ref MSG_C.
-*/
/** \defgroup MSG_C MSG native
\ingroup MSG_API
- \ref MSG_ext_icomms_Receiver
- \ref MSG_ext_icomms_core
- \ref MSG_ext_icomms_Main
- - \ref MSG_ext_icomms_fct
+ - \ref MSG_ext_icomms_fct_Waitall
+ - \ref MSG_ext_icomms_fct_Waitany
<hr>
- \ref MSG_ext_ms_platform
- \dontinclude lua/master_slave.lua
+ \dontinclude lua/masterslave/master_slave.lua
\section MSG_ext_ms_code_lua Code of the application
- \ref MSG_ext_ms_core_lua
- \dontinclude lua/master_slave_bypass.lua
+ \dontinclude lua/console/master_slave_bypass.lua
\section MSG_ext_ms_code_lua Code of the application
