Commit 0169468c authored by Stepan Kasal's avatar Stepan Kasal

Fix typos: invokation -> invocation.

parent 833abd55
2005-08-10 Stepan Kasal <kasal@ucw.cz>
Fix typos: Invokation --> Invocation (in various places)
2005-08-10 Matthias Clasen <mclasen@redhat.com>
* glib/gfileutils.c (g_build_path_va, g_build_pathname_va):
......
......@@ -462,12 +462,12 @@ Sun Jan 17 14:13:52 1999 Tim Janik <timj@gtk.org>
* gmain.c (g_source_add): set hook_destroy to G_HOOK_DEFERRED_DESTROY,
instead of using an ugly _noop() hack, this is to avoid an uneccessary
function invokation. set hook_free to g_source_destroy_func, this way
function invocation. set hook_free to g_source_destroy_func, this way
we always invoke the destroy notifiers for user_data and source_data
after execution of dispatch(). thus, g_source_destroy_func() will always
be called within the main_loop lock (this wasn't really assured
before), and can release and reaquire the look around destroy notifier
invokation.
invocation.
Sun Jan 17 11:01:40 1999 Tor Lillqvist <tml@iki.fi>
......@@ -1769,7 +1769,7 @@ Thu Oct 8 06:47:27 1998 Tim Janik <timj@gtk.org>
added new functions g_dataset_id_remove_no_notify and
g_datalist_id_remove_no_notify plus associated macros
g_dataset_remove_no_notify and g_datalist_remove_no_notify, which
will remove a certain data portion without invokation of its destroy
will remove a certain data portion without invocation of its destroy
notifier, this should only be used in very controled circumstances.
Wed Oct 7 05:31:24 1998 Tim Janik <timj@gtk.org>
......@@ -1860,7 +1860,7 @@ Mon Sep 21 02:22:12 1998 Tim Janik <timj@gtk.org>
* ghash.c: added some g_return_if_fail() statements. make
g_hash_table_lookup_node() an inline function so we save an extra
function invokation on lookups.
function invocation on lookups.
Sun Sep 20 18:21:46 1998 Owen Taylor <otaylor@redhat.com>
......@@ -2081,7 +2081,7 @@ Mon Aug 24 02:08:56 1998 Tim Janik <timj@gtk.org>
removed g_attach_process().
g_on_error_stack_trace() should probably be handled with caution,
i've seem several different linux versions (2.0.x) become unstable
after invokation of this function.
after invocation of this function.
1998-08-18: Elliot Lee <sopwith@redhat.com>
......
......@@ -6777,7 +6777,7 @@ Mon Mar 22 03:54:43 1999 Tim Janik <timj@gtk.org>
functions, so it can be used to e.g. pass a GPollFd.
(g_main_poll): only add poll records with an events mask != 0 to the
fd_array. don't even bother calling poll_func() if fds=timeout=0.
added debugging printouts around poll_func() invokation that can be
added debugging printouts around poll_func() invocation that can be
enabled with #define G_MAIN_POLL_DEBUG.
Fri Mar 19 16:29:50 PST 1999 Manish Singh <yosh@gimp.org>
......
2005-08-10 Stepan Kasal <kasal@ucw.cz>
Fix typos: Invokation --> Invocation (in various places)
2005-08-10 Matthias Clasen <mclasen@redhat.com>
* glib/gfileutils.c (g_build_path_va, g_build_pathname_va):
......
2005-08-10 Stepan Kasal <kasal@ucw.cz>
Fix typos: Invokation --> Invocation (in various places)
2005-08-10 Matthias Clasen <mclasen@redhat.com>
* glib/gfileutils.c (g_build_path_va, g_build_pathname_va):
......
2005-08-10 Stepan Kasal <kasal@ucw.cz>
Fix typos: Invokation --> Invocation (in various places)
2005-08-10 Matthias Clasen <mclasen@redhat.com>
* glib/gfileutils.c (g_build_path_va, g_build_pathname_va):
......
2005-08-10 Stepan Kasal <kasal@ucw.cz>
Fix typos: Invokation --> Invocation (in various places)
2005-08-05 Matthias Clasen <mclasen@redhat.com>
* gobject/tmpl/gparamspec.sgml:
......
......@@ -34,7 +34,7 @@ $ pkg-config --libs glib-2.0
<para>
If your application uses modules, threads or <structname>GObject</structname>
features, it must be compiled and linked with the options returned by the
following <application>pkg-config</application> invokations:
following <application>pkg-config</application> invocations:
<programlisting>
$ pkg-config --cflags --libs gmodule-2.0
$ pkg-config --cflags --libs gthread-2.0
......
......@@ -190,7 +190,7 @@ Calls the given function for each data element of the datalist.
The function is called with each data element's #GQuark id and data,
together with the given @user_data parameter.
Note that this function is NOT thread-safe. So unless @datalist
can be protected from any modifications during invokation of this
can be protected from any modifications during invocation of this
function, it should not be called.
</para>
......
......@@ -180,7 +180,7 @@ Removes an element, without calling its destroy notifier.
Calls the given function for each data element which is associated with the
given location.
Note that this function is NOT thread-safe. So unless @datalist
can be protected from any modifications during invokation of this
can be protected from any modifications during invocation of this
function, it should not be called.
</para>
......
......@@ -31,7 +31,7 @@ collect its return value.
</para>
</refsect1>
<refsect1><title>Invokation</title>
<refsect1><title>Invocation</title>
<para>
<command>glib-genmarshal</command> takes a list of marshallers to generate as
input. The marshaller list is either read from standard input or from files
......
......@@ -28,7 +28,7 @@ value name strings for introspection.
</para>
</refsect1>
<refsect1><title>Invokation</title>
<refsect1><title>Invocation</title>
<para>
<command>glib-mkenums</command> takes a list of valid C code files as
input. The options specified control the text that is output, certain
......
......@@ -30,7 +30,7 @@ types.
</para>
</refsect1>
<refsect1><title>Invokation</title>
<refsect1><title>Invocation</title>
<para>
<command>gobject-query</command> takes a mandatory argument that specifies
whether it should iterate over the fundamental types or print a type tree.
......
......@@ -909,7 +909,7 @@ identified by @itype.
A predefined #GSignalAccumulator for signals that return a
boolean values. The behavior that this accumulator gives is
that a return of %TRUE stops the signal emission: no further
callbacks will be invokced, while a return of %FALSE allows
callbacks will be invoked, while a return of %FALSE allows
the emission to coninue. The idea here is that a %TRUE return
indicates that the callback <emphasis>handled</emphasis> the signal,
and no further handling is needed.
......
......@@ -236,7 +236,7 @@ g_data_set_internal (GData **datalist,
G_DATALIST_SET_POINTER (datalist, list->next);
/* the dataset destruction *must* be done
* prior to invokation of the data destroy function
* prior to invocation of the data destroy function
*/
if (!list->next && dataset)
g_dataset_destroy_internal (dataset);
......@@ -295,7 +295,7 @@ g_data_set_internal (GData **datalist,
list->destroy_func = destroy_func;
/* we need to have updated all structures prior to
* invokation of the destroy function
* invocation of the destroy function
*/
G_UNLOCK (g_dataset_global);
dfunc (ddata);
......
......@@ -2501,8 +2501,8 @@ Fri Oct 27 16:33:41 2000 Tim Janik <timj@gtk.org>
that gets passed in to closure invocations. added signal details.
renamed GSignalType to GSignalFlags to comply with conventions.
quite some cleanups and minor fixes. avoid uneccessary handler list
walks upon invokation of after handlers. relookup handler list for
restarted emissions. preliminary abort normal handler invokation if
walks upon invocation of after handlers. relookup handler list for
restarted emissions. preliminary abort normal handler invocation if
after handler is encountered.
* glib-genmarshal.c:
......
......@@ -55,7 +55,7 @@
* a write lock or more than 0 read locks have to be held across
* function invocation
* - _W: [Write-locked invocation]
* a write lock has to be held across function invokation
* a write lock has to be held across function invocation
* - _Wm: [Write-locked invocation, mutatable]
* like _W, but the write lock might be released and reacquired
* during invocation, watch your pointers
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment