From c53d0aac5a5ab41701f3320d95f1cd2b0f3fd005 Mon Sep 17 00:00:00 2001 From: navarro Date: Wed, 30 May 2012 11:23:41 +0200 Subject: [PATCH] Some typos in source code --- ChangeLog | 2 +- doc/Doxyfile.in | 2 +- doc/bindings.doc | 6 ++--- doc/gtut-introduction.doc | 12 +++++----- doc/gtut-tour-02-simple.doc | 8 +++---- doc/gtut-tour-03-args.doc | 2 +- doc/gtut-tour-04-callback.doc | 2 +- doc/gtut-tour-05-globals.doc | 8 +++---- doc/gtut-tour-06-logs.doc | 2 +- doc/gtut-tour-07-timers.doc | 8 +++---- doc/gtut-tour-08-exceptions.doc | 4 ++-- doc/gtut-tour-09-simpledata.doc | 4 ++-- doc/gtut-tour-10-rpc.doc | 2 +- doc/gtut-tour-11-explicitwait.doc | 6 ++--- doc/gtut-tour-recap-messages.doc | 2 +- doc/module-gras.doc | 24 +++++++++---------- doc/module-msg.doc | 14 +++++------ doc/surf_nutshell.fig | 2 +- examples/gras/console/ping_server.c | 2 +- examples/gras/mmrpc/mmrpc.c | 2 +- examples/gras/mmrpc/mmrpc_server.c | 2 +- .../simple_token/simple_token.c | 2 +- examples/gras/ping/ping_server.c | 2 +- examples/gras/rpc/rpc.c | 2 +- .../deployment_duplicated_globals.xml | 4 ++-- .../lua/state_cloner/duplicated_globals.lua | 12 +++++----- .../lua/state_cloner/duplicated_globals.tesh | 6 ++--- include/gras/messages.h | 8 +++---- include/gras/timer.h | 2 +- include/xbt/config.h | 2 +- include/xbt/datadesc.h | 2 +- include/xbt/dynar.h | 2 +- include/xbt/ex.h | 2 +- src/bindings/lua/simgrid_lua.c | 2 +- src/gras/Msg/gras_msg_exchange.c | 10 ++++---- src/gras/Msg/gras_msg_listener.c | 8 +++---- src/gras/Virtu/virtu_private.h | 2 +- src/surf/surf.c | 2 +- src/xbt/datadesc/cbps.c | 4 ++-- src/xbt/datadesc/datadesc_private.h | 2 +- src/xbt/log.c | 2 +- 41 files changed, 97 insertions(+), 97 deletions(-) diff --git a/ChangeLog b/ChangeLog index 463d8fa791..31f8f51792 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1210,7 +1210,7 @@ SimGrid (3.3) stable; urgency=high [contributed by Sékou Diakite, many thanks] GRAS: - * Introduce a listener thread in charge of receiving incomming + * Introduce a listener thread in charge of receiving incoming messages from the network. It allows to overlap communication and computation but most notably, it removes some stupid deadlocks due to the fact that so far, a process could not send and receive at diff --git a/doc/Doxyfile.in b/doc/Doxyfile.in index f36aa29736..bd4d33327a 100644 --- a/doc/Doxyfile.in +++ b/doc/Doxyfile.in @@ -781,7 +781,7 @@ EXAMPLE_PATH = ./ \ EXAMPLE_PATTERNS = # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be -# searched for input files to be used with the \include or \dontinclude +# searched for input files to be used with the \include or \don'tinclude # commands irrespective of the value of the RECURSIVE tag. # Possible values are YES and NO. If left blank NO is used. diff --git a/doc/bindings.doc b/doc/bindings.doc index 5c25bf98a4..a3265323e0 100644 --- a/doc/bindings.doc +++ b/doc/bindings.doc @@ -32,7 +32,7 @@ Actually, the use of lua in Simgrid is quite simple, you have just to follow the - loading the platforme/deployment XML file that describe the environment of simulation - and … Running the Simulation. -\dontinclude lua/masterslave/master.lua +\don'tinclude lua/masterslave/master.lua \subsection bindings_binding_lua_example_master_slave Master/Slave Example \li Master Code @@ -41,13 +41,13 @@ we mainly use simgrid.Task.new(task_name,computation_size,communication_size) then simgrid.Task.send(task,alias) to send it. we use also simgrid.Task.name(task), to get the task's name. -\dontinclude lua/masterslave/slave.lua +\don'tinclude lua/masterslave/slave.lua \li Slave Code \until end_of_slave Here, we see the use of simgrid.Task.recv(alias) to receive a task with a specific alias, this function return directly the task recevied. -\dontinclude lua/masterslave/master_slave.lua +\don'tinclude lua/masterslave/master_slave.lua \li Set Environmenet and run application \until simgrid.clean() diff --git a/doc/gtut-introduction.doc b/doc/gtut-introduction.doc index 71720918a6..01afc6bdbb 100644 --- a/doc/gtut-introduction.doc +++ b/doc/gtut-introduction.doc @@ -209,7 +209,7 @@ Two main types of events may change the internal state of a given process: messages during the transition associated to this event.\n \n Incoming messages are not handled as soon as they arrive, but only when - the process declares to be ready to accept incomming events (using \ref + the process declares to be ready to accept incoming events (using \ref gras_msg_handle or related functions). It ensures that the treatment of a given message won't run in parallel to any other callback, so that process globals (its state) can be accessed and modified without @@ -221,7 +221,7 @@ Two main types of events may change the internal state of a given process: \n Processes can also wait explicitely for incoming messages matching some given criterions (using \ref gras_msg_wait). Any messages received before the - one matching the criterions will be added to the incomming messages' + one matching the criterions will be added to the incoming messages' queue for further use. This may breaks the message delivery order. Moreover, there is no restriction on when this can be done. So, a callback to a given message can consume messages of other types. There is @@ -287,14 +287,14 @@ The experimental scenario is as follows: