X-Git-Url: http://info.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/blobdiff_plain/902d2be616da66488e2ef2c2066f47d651a27f6c..00eb4a59a0a98fbe1ffef38f52562872631a8e76:/docs/source/app_s4u.rst diff --git a/docs/source/app_s4u.rst b/docs/source/app_s4u.rst index 3f6767b8bf..5bfdc53795 100644 --- a/docs/source/app_s4u.rst +++ b/docs/source/app_s4u.rst @@ -8,8 +8,8 @@ The S4U Interface
@@ -343,14 +343,13 @@ Memory Management For sake of simplicity, we use `RAII `_ -everywhere in S4U. This is an idiom where resources are automatically +for many classes in S4U. This is an idiom where resources are automatically managed through the context. Provided that you never manipulate objects of type Foo directly but always FooPtr references (which are defined as `boost::intrusive_ptr `_ ), you will never have to explicitely release the resource that you use nor to free the memory of unused objects. - Here is a little example: .. code-block:: cpp @@ -365,6 +364,11 @@ Here is a little example: } // The mutex gets automatically freed because the only existing reference gets out of scope +Note that Mailboxes, Hosts and Links are not handled thought smart +pointers (yet?). This means that it is currently impossible to destroy a +mailbox or a link. You can still destroy an host (but probably +shouldn't), using :cpp:func:`simgrid::s4u::Host::destroy`. + C++ API Reference ***************** @@ -464,6 +468,32 @@ s4u::Exec :protected-members: :undoc-members: +.. _API_s4u_ExecSeq: + +============ +s4u::ExecSeq +============ + +.. doxygentypedef:: ExecSeqPtr + +.. doxygenclass:: simgrid::s4u::ExecSeq + :members: + :protected-members: + :undoc-members: + +.. _API_s4u_ExecPar: + +============ +s4u::ExecPar +============ + +.. doxygentypedef:: ExecParPtr + +.. doxygenclass:: simgrid::s4u::ExecPar + :members: + :protected-members: + :undoc-members: + .. _API_s4u_Host: =========