study on your :ref:`simulated platform <platform>`, i.e. to specify which actor
should be started on which host. You can do so directly in your program (as
shown in :ref:`these examples <s4u_ex_actors>`), or using an XML deployment
-file. Unless you have a good reason, you should keep your application apart
+file. Either way, it is a good habit to keep your application apart
from the deployment as it will :ref:`ease your experimental campaign afterward
<howto_science>`.
<argument value="3000"/>
</actor>
- <!-- Carole runs on 'host3', has 1 parameter "42" in its argv and one property.
+ <!-- Carole runs on 'host3', has 1 parameter "42" in its argv and one property.
-- Use simgrid::s4u::Actor::get_property() to retrieve it.-->
<actor host="host3" function="carol">
<argument value="42"/>
<actor>
--------
-This tag starts a new actor executing the given function on a given host.
+This tag starts a new actor executing the given function on a given host.
**Parent tags:** :ref:`pf_tag_platform` (only in deployment files) |br|
with :cpp:func:`simgrid::s4u::Engine::register_actor` or
with :cpp:func:`simgrid::s4u::Engine::register_function`.
- If you are stuck with MSG, use :cpp:func:`MSG_process_create`,
- :cpp:func:`MSG_process_create_with_arguments` or
- :cpp:func:`MSG_process_create_with_environment`.
-
- There is nothing to do in Java, as SimGrid uses introspection abilities to
- retrieve the classes from their names. You must then use the full class name
- (including the package name) in your XML file.
-
:``start_time``: Useful to delay the start of your actor.
-1 starts the actor immediately.
