From: Martin Quinson Date: Fri, 14 Oct 2016 10:39:27 +0000 (+0200) Subject: point to the MSG doc, not the XBT one on synchro. It's less awfull X-Git-Tag: v3_14~340 X-Git-Url: http://info.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/commitdiff_plain/10cf0994b175d422edd693db91f25a96418b6862?ds=sidebyside point to the MSG doc, not the XBT one on synchro. It's less awfull --- diff --git a/doc/doxygen/FAQ.doc b/doc/doxygen/FAQ.doc index 52e405e78a..1991d94b5b 100644 --- a/doc/doxygen/FAQ.doc +++ b/doc/doxygen/FAQ.doc @@ -172,8 +172,8 @@ deadlock. Instead, you should use the synchronization mechanism provided by the simulation kernel. This could with a SimGrid mutex, a SimGrid -condition variables or a SimGrid semaphore, as described in \ref -XBT_synchro (in Java, only semaphores are available). But actually, +condition variables or a SimGrid semaphore, as described in @ref +msg_synchro (in Java, only semaphores are available). But actually, many synchronization patterns can be encoded with communication on mailboxes. Typically, if you need one process to notify another one, you could use a condition variable or a semphore, but sending a