Typo fixes.

* glib/tmpl/memory.sgml: Typo fixes.
This commit is contained in:
Matthias Clasen 2001-12-15 19:29:20 +00:00
parent 9e4e61360b
commit d6977cf92f
2 changed files with 6 additions and 2 deletions

View File

@ -1,3 +1,7 @@
2001-12-14 Matthias Clasen <matthias@poet.de>
* glib/tmpl/memory.sgml: Typo fixes.
2001-12-13 Matthias Clasen <matthiasc@poet.de>
* glib/tmpl/completion.sgml, glib/tmpl/date.sgml,

View File

@ -133,13 +133,13 @@ Thus it provides the same advantages and pitfalls as <function>alloca()</functio
the stack pointer register.
</para></listitem></varlistentry>
<varlistentry><term></term><listitem><para>
+ It doesn't cause any memory fragmentation, within its scope, seperate alloca()
+ It doesn't cause any memory fragmentation, within its scope, separate <function>alloca()</function>
blocks just build up and are released together at function end.
</para></listitem></varlistentry>
<varlistentry><term></term><listitem><para>
- Allocation sizes have to fit into the current stack frame. For instance in a
threaded environment on Linux, the per-thread stack size is limited to 2 Megabytes,
so be sparse with <funcion>alloca()</function> uses.
so be sparse with <function>alloca()</function> uses.
</para></listitem></varlistentry>
<varlistentry><term></term><listitem><para>
- Allocation failure due to insufficient stack space is not indicated with a %NULL