From: Laurent Bobelin Date: Wed, 16 Nov 2011 09:47:49 +0000 (+0100) Subject: Corrected typos as I had 5 minutes to waste before a meeting at 11. X-Git-Tag: v3_9_90~569^2~19^2~161 X-Git-Url: http://info.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/commitdiff_plain/4360c655a388faa67e07bf1131772d566fc555a2 Corrected typos as I had 5 minutes to waste before a meeting at 11. --- diff --git a/doc/index.doc b/doc/index.doc index 490db7d57c..b742f82d19 100644 --- a/doc/index.doc +++ b/doc/index.doc @@ -8,23 +8,23 @@ MSG was the first distributed programming environment provided within SimGrid. W \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. SimGrid-java let you use MSG while coding in Java. So if your need is MSG + Java, you're in the right section ! +given problem you don't really want to implement. SimGrid-java let you use MSG while coding in Java. So if your need is MSG + Java, you're in the right section! -\section SimGrid-java usage overview +\section SimGrid-java Usage overview -To make a long story short, it's a JNI binding, so it implies that : +To make a long story short, it's a JNI binding, so it implies that: \li Most of the MSG and SimGrid documentation about behavioral aspects applies directly to what you are programming. -\li MSG data structures are mapped to Java objects. So it means that from the syntaxic point of view, you have to know how those objects are. Fortunately, we have generated the Javadoc for those objects. So take a look at it +\li MSG data structures are mapped to Java objects. So it means that from the syntax point of view, you have to know how those objects are. Fortunately, we have generated the Javadoc for those objects. So take a look at it -Finally, it implies also that your program can crash for 3 main reasons : +Finally, it implies also that your program can crash for 3 main reasons: -\li Your Java part is not good : you'll have a good old java exception thrown, and hence you should be able to correct it by yourself. -\li Our java part is not good : you'll also have a java exception thrown, but we have real doubts this can happen, since the java part is only a JNI binding. The other option is that it crashed because you used incorrectly the MSG API, so this means also you should have a MSGException. It means you should read carefully MSG samples and/or documentation. +\li Your Java part is not good: you'll have a good old java exception thrown, and hence you should be able to correct it by yourself. +\li Our java part is not good: you'll also have a java exception thrown, but we have real doubts this can happen, since the java part is only a JNI binding. The other option is that it crashed because you used incorrectly the MSG API, so this means also you should have an MSGException. It means you should read carefully MSG samples and/or documentation. \li Something has crashed in the C part. Okay, here comes the tricky thing. -C crashes mainly for 2 reasons : +C crashes mainly for 2 reasons: \li When something goes wrong in your simulation, sometimes the C part stops because you used SimGrid incorrectly, and JNI bindings are not fond of that. It means that you'll have something that looks ugly, but you should be able to identify what's going wrong in your code by carefully reading the whole error message -\li It may happen that the problem comes directly from SimGrid : in this case, the error should be uglier. In that case, you may submit a bug directly to SimGrid. +\li It may happen that the problem comes directly from SimGrid: in this case, the error should be uglier. In that case, you may submit a bug directly to SimGrid. */