luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2025-03-25 00:50:05 +01:00
Code Issues Packages Projects Releases Wiki Activity

fix internal link, little XXX cleanup

Browse Source 
* gobject/tut_gtype.xml:
fix internal link, little XXX cleanup
This commit is contained in:
Stefan Kost 2006-01-07 21:08:17 +00:00
parent b1f3e98461
commit fbaf1c4db6
2 changed files with 68 additions and 61 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/reference/ChangeLog
View File

@ -1,3 +1,8 @@
2006-01-07 Stefan Kost <ensonic@users.sf.net>
* gobject/tut_gtype.xml:
fix internal link, little XXX cleanup
2006-01-05 Matthias Clasen <mclasen@redhat.com>
* === Released 2.9.2 ===

14
docs/reference/gobject/tut_gtype.xml
View File

@ -97,7 +97,7 @@ GType g_type_register_fundamental (GType type_id,
<type><link linkend="GTypeInfo">GTypeInfo</link></type>.
</para></listitem>
<listitem><para>
XXX: <type><link linkend="GTypeFlags">GTypeFlags</link></type>.
type characteristic flags: <type><link linkend="GTypeFlags">GTypeFlags</link></type>.
</para></listitem>
</itemizedlist>
Fundamental types are also defined by a set of <type><link linkend="GTypeFundamentalFlags">GTypeFundamentalFlags</link></type>
@ -251,8 +251,7 @@ struct _GTypeValueTable
returns a pointer of type <type>PrefixObject</type>. This macro is used to enforce
static type safety by doing explicit casts wherever needed. It also enforces
dynamic type safety by doing runtime checks. It is possible to disable the dynamic
type checks in production builds (see
<ulink>http://developer.gnome.org/doc/API/2.0/glib/glib-building.html</ulink>).
type checks in production builds (see <link linkend="glib-building">building glib</link>).
For example, we would create
<function>MAMAN_BAR (obj)</function> to keep the previous example.
</para></listitem>
@ -261,10 +260,12 @@ struct _GTypeValueTable
is strictly equivalent to the previous casting macro: it does static casting with
dynamic type checking of class structures. It is expected to return a pointer
to a class structure of type <type>PrefixObjectClass</type>. Again, an example is:
<function>MAMAN_BAR_CLASS</function>.</para></listitem>
<function>MAMAN_BAR_CLASS</function>.
</para></listitem>
<listitem><para>Create a macro named <function>PREFIX_IS_BAR (obj)</function>: this macro is expected
to return a <type>gboolean</type> which indicates whether or not the input
object instance pointer of type BAR.</para></listitem>
object instance pointer of type BAR.
</para></listitem>
<listitem><para>If the type is classed, create a macro named
<function>PREFIX_IS_OBJECT_CLASS (klass)</function> which, as above, returns a boolean
if the input class pointer is a pointer to a class of type OBJECT.
@ -273,7 +274,8 @@ struct _GTypeValueTable
<function>PREFIX_OBJECT_GET_CLASS (obj)</function>
which returns the class pointer associated to an instance of a given type. This macro
is used for static and dynamic type safety purposes (just like the previous casting
macros).</para></listitem>
macros).
</para></listitem>
</itemizedlist>
The implementation of these macros is pretty straightforward: a number of simple-to-use
macros are provided in <filename>gtype.h</filename>. For the example we used above, we would