Symbian3/SDK/Source/GUID-4ADD8234-4AFD-4E80-94A4-AC018FE83276.dita
changeset 13 48780e181b38
parent 8 ae94777fff8f
equal deleted inserted replaced
12:80ef3a206772 13:48780e181b38
    16 <ul>
    16 <ul>
    17 <li><p>Memory allocation</p></li>
    17 <li><p>Memory allocation</p></li>
    18 <li><p>Spawn APIs</p></li>
    18 <li><p>Spawn APIs</p></li>
    19 <li><p>Libgmodule APIs </p></li>
    19 <li><p>Libgmodule APIs </p></li>
    20 </ul>
    20 </ul>
    21 <section id="GUID-DFAD39D6-BA92-4293-B5EC-97077CE1FC1A-GENID-1-10-1-11-1-1-7-1-6-1-4-1-3-3">       <title>Memory
    21 <section id="GUID-DFAD39D6-BA92-4293-B5EC-97077CE1FC1A-GENID-1-10-1-13-1-1-7-1-6-1-4-1-3-3">       <title>Memory
    22 allocation</title>       <p>The Symbian GLib implementation does not follow
    22 allocation</title>       <p>The Symbian GLib implementation does not follow
    23 the default OSS behavior. The default OSS behavior is such that in the event
    23 the default OSS behavior. The default OSS behavior is such that in the event
    24 of a memory allocation failure the application, using <codeph>g_malloc()</codeph> and
    24 of a memory allocation failure the application, using <codeph>g_malloc()</codeph> and
    25 not <codeph>g_try_malloc()</codeph>, will call <codeph>abort()</codeph> and
    25 not <codeph>g_try_malloc()</codeph>, will call <codeph>abort()</codeph> and
    26 thus terminate the application.  </p><p>The Symbian implementation, on the
    26 thus terminate the application.  </p><p>The Symbian implementation, on the
    28 of a memory allocation failure. Thus, it is the application’s responsibility
    28 of a memory allocation failure. Thus, it is the application’s responsibility
    29 to check if the memory allocation failed due to the needed tasks.</p><p>Generally,
    29 to check if the memory allocation failed due to the needed tasks.</p><p>Generally,
    30 all the application code written using GLib does not perform memory allocation
    30 all the application code written using GLib does not perform memory allocation
    31 failure checks. Hence, for Symbian GLib it is the application programmer's
    31 failure checks. Hence, for Symbian GLib it is the application programmer's
    32 responsibility to check for memory allocation failures.  </p>     </section>
    32 responsibility to check for memory allocation failures.  </p>     </section>
    33 <section id="GUID-DFAD39D6-BA92-4293-B5EC-97077CE1FC1A-GENID-1-10-1-11-1-1-7-1-6-1-4-1-3-4">       <title>Spawn
    33 <section id="GUID-DFAD39D6-BA92-4293-B5EC-97077CE1FC1A-GENID-1-10-1-13-1-1-7-1-6-1-4-1-3-4">       <title>Spawn
    34 APIs</title>       <p>GLib has a set of APIs for process spawning. Since Symbian
    34 APIs</title>       <p>GLib has a set of APIs for process spawning. Since Symbian
    35 platform does not support the <codeph>fork()</codeph> and <codeph>exec()</codeph> APIs,
    35 platform does not support the <codeph>fork()</codeph> and <codeph>exec()</codeph> APIs,
    36 the <codeph>g_spawn*</codeph> APIs have limitations in their functionality.
    36 the <codeph>g_spawn*</codeph> APIs have limitations in their functionality.
    37 The limitations are explained per API in detail below.</p><p><b><codeph>g_spawn_async_with_pipes</codeph></b></p><p>The
    37 The limitations are explained per API in detail below.</p><p><b><codeph>g_spawn_async_with_pipes</codeph></b></p><p>The
    38 signature of this API is:</p><codeblock xml:space="preserve">gboolean g_spawn_async_with_pipes (
    38 signature of this API is:</p><codeblock xml:space="preserve">gboolean g_spawn_async_with_pipes (