errno.h and sys/stat/h are always here nowadays

[simgrid.git] / doc / doxygen / FAQ.doc

diff --git a/doc/doxygen/FAQ.doc b/doc/doxygen/FAQ.doc
index 9b1dd1d..0cdd751 100644 (file)
--- a/doc/doxygen/FAQ.doc
+++ b/doc/doxygen/FAQ.doc
@@ -49,19 +49,16 @@ We also have a more graphical output. Have a look at section \ref options_tracin
 
 \subsection faq_C Argh! Do I really have to code in C?
 
 
 \subsection faq_C Argh! Do I really have to code in C?
 

-Currently bindings on top of MSG are supported for Java, Ruby and Lua. You can find a few
-documentation about them on the doc page. Note that bindings are released separately from the main dist
-and so have their own version numbers.
+We provide Java bindings of the MSG interface, which is the main
+SimGrid user API.

 
 

-Moreover If you use C++,
-you should be able to use the SimGrid library as a standard C library
-and everything should work fine (simply <i>link</i> against this
-library; recompiling SimGrid with a C++ compiler won't work and it
-wouldn't help if you could).
+Moreover If you use C++, you should be able to use the SimGrid library
+as a standard C library and everything should work fine (simply
+<i>link</i> against this library; recompiling SimGrid with a C++
+compiler won't work and it wouldn't help if you could).

 
 

-For now,
-we do not feel a real demand for any other language. But if you think there is one,
- please speak up!
+For now, we do not feel a real demand for any other language. But if
+you think there is one, please speak up!

 
 \section faq_howto Feature related questions
 
 
 \section faq_howto Feature related questions
 


@@ -193,7 +190,7 @@ would have to do out of the simulator, and thus gives you information that
 you could also get in real settings to not hinder the realism of your
 simulation.
 
 you could also get in real settings to not hinder the realism of your
 simulation.
 

-\verbatim
+\code

 double get_host_load() {
    m_task_t task = MSG_task_create("test", 0.001, 0, NULL);
    double date = MSG_get_clock();
 double get_host_load() {
    m_task_t task = MSG_task_create("test", 0.001, 0, NULL);
    double date = MSG_get_clock();


@@ -203,7 +200,7 @@ double get_host_load() {
    MSG_task_destroy(task);
    return (0.001/date);
 }
    MSG_task_destroy(task);
    return (0.001/date);
 }

-\endverbatim
+\endcode

 
 Of course, it may not match your personal definition of "host load". In this
 case, please detail what you mean on the mailing list, and we will extend
 
 Of course, it may not match your personal definition of "host load". In this
 case, please detail what you mean on the mailing list, and we will extend


@@ -218,7 +215,7 @@ account the time spent waiting for the other party to be
 ready). However, getting the *real* communication time is not really
 hard either. The following solution is a good starting point.
 
 ready). However, getting the *real* communication time is not really
 hard either. The following solution is a good starting point.
 

-\verbatim
+\code

 int sender()
 {
   m_task_t task = MSG_task_create("Task", task_comp_size, task_comm_size,
 int sender()
 {
   m_task_t task = MSG_task_create("Task", task_comp_size, task_comm_size,


@@ -243,7 +240,7 @@ int receiver()
   MSG_task_destroy(task);
   return 0;
 }
   MSG_task_destroy(task);
   return 0;
 }

-\endverbatim
+\endcode

 
 \subsection faq_MIA_SimDag SimDag related questions
 
 
 \subsection faq_MIA_SimDag SimDag related questions
 


@@ -256,10 +253,10 @@ model a data dependency between two DAG tasks t1 and t2, you have to
 create 3 SD_tasks: t1, t2 and c and add dependencies in the following
 way:
 
 create 3 SD_tasks: t1, t2 and c and add dependencies in the following
 way:
 

-\verbatim
+\code

 SD_task_dependency_add(NULL, NULL, t1, c);
 SD_task_dependency_add(NULL, NULL, c, t2);
 SD_task_dependency_add(NULL, NULL, t1, c);
 SD_task_dependency_add(NULL, NULL, c, t2);

-\endverbatim
+\endcode

 
 This way task t2 cannot start before the termination of communication c
 which in turn cannot start before t1 ends.
 
 This way task t2 cannot start before the termination of communication c
 which in turn cannot start before t1 ends.


@@ -281,7 +278,7 @@ communicating process to make the whole scheduling process
 distributed. Here is an example of how you could do that. Assume T1
 has to be done before T2.
 
 distributed. Here is an example of how you could do that. Assume T1
 has to be done before T2.
 

-\verbatim
+\code

  int your_agent(int argc, char *argv[] {
    ...
    T1 = MSG_task_create(...);
  int your_agent(int argc, char *argv[] {
    ...
    T1 = MSG_task_create(...);


@@ -298,7 +295,7 @@ has to be done before T2.
      }
    }
  }
      }
    }
  }

-\endverbatim
+\endcode

 
 If you decide that the distributed part is not that much important and that
 DAG is really the level of abstraction you want to work with, then you should
 
 If you decide that the distributed part is not that much important and that
 DAG is really the level of abstraction you want to work with, then you should