-/** \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
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 C programming language, your are in the right
- section. To use the Java programming interface, please refer to
- \ref MSG_JAVA.
+ section. To use the Java or Ruby programming interfaces, please refer to
+ the documentation provided in the relevant packages.
*/
/** @addtogroup MSG_LUA
\section MSG_Lua_funct Lua offered functionnalities in MSG
- - \ref host_management
- - \ref tasks_management
- - \ref environment_management
+ - \ref lua_host_management
+ - \ref lua_tasks_management
+ - \ref lua_environment_management
\section Lua_examples Examples of lua MSG
- \ref MSG_ex_master_slave_lua
- \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>
\dontinclude msg/icomms/peer2.c
- \section MSG_ext_icomms_fct Waitall function for sender
+ \section MSG_ext_icomms_fct_Waitall Waitall function for sender
The use of this function permit to send all messages and wait for the completion of all in one time.
\skipline Sender function
\until end_of_sender
+ \section MSG_ext_icomms_fct_Waitany Waitany function
+
+ The MSG_comm_waitany() function return the place of the first message send or receive from a xbt_dynar_t table.
+
+ \subsection MSG_ext_icomms_fct_Waitany_sender From a sender
+ We can use this function to wait all sended messages.
+ \dontinclude msg/icomms/peer3.c
+ \skipline Sender function
+ \until end_of_sender
+
+ \subsection MSG_ext_icomms_fct_Waitany_receiver From a receiver
+ We can also wait for the receiving of all messages.
+ \dontinclude msg/icomms/peer3.c
+ \skipline Receiver function
+ \until end_of_receiver
+
*/
/** \page MSG_ex_master_slave_scrip_lua Master/slave application using lua console
- \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
