Skip to content

Commit

Permalink
Update GIR files
Browse files Browse the repository at this point in the history
  • Loading branch information
sdroege authored and github-actions[bot] committed Aug 11, 2024
1 parent 4d11891 commit 39dac97
Show file tree
Hide file tree
Showing 10 changed files with 5,256 additions and 1,041 deletions.
6 changes: 3 additions & 3 deletions Atk-1.0.gir
Original file line number Diff line number Diff line change
Expand Up @@ -553,7 +553,7 @@ A string name/value pair representing a generic attribute.</doc>
</parameters>
</function>
</record>
<constant name="BINARY_AGE" value="25210" c:type="ATK_BINARY_AGE" version="2.7.4">
<constant name="BINARY_AGE" value="25311" c:type="ATK_BINARY_AGE" version="2.7.4">
<doc xml:space="preserve">Like atk_get_binary_age(), but from the headers used at
application compile time, rather than from the library linked
against at application run time.</doc>
Expand Down Expand Up @@ -4721,13 +4721,13 @@ application compile time, rather than from the library linked
against at application run time.</doc>
<type name="gint" c:type="gint"/>
</constant>
<constant name="MICRO_VERSION" value="0" c:type="ATK_MICRO_VERSION" version="2.7.4">
<constant name="MICRO_VERSION" value="1" c:type="ATK_MICRO_VERSION" version="2.7.4">
<doc xml:space="preserve">Like atk_get_micro_version(), but from the headers used at
application compile time, rather than from the library linked
against at application run time.</doc>
<type name="gint" c:type="gint"/>
</constant>
<constant name="MINOR_VERSION" value="52" c:type="ATK_MINOR_VERSION" version="2.7.4">
<constant name="MINOR_VERSION" value="53" c:type="ATK_MINOR_VERSION" version="2.7.4">
<doc xml:space="preserve">Like atk_get_minor_version(), but from the headers used at
application compile time, rather than from the library linked
against at application run time.</doc>
Expand Down
110 changes: 102 additions & 8 deletions GLib-2.0.gir
Original file line number Diff line number Diff line change
Expand Up @@ -15203,7 +15203,7 @@ linked against at application run time.</doc>
<constant name="MAXUINT8" value="255" c:type="G_MAXUINT8">
<type name="guint8" c:type="guint8"/>
</constant>
<constant name="MICRO_VERSION" value="0" c:type="GLIB_MICRO_VERSION">
<constant name="MICRO_VERSION" value="2" c:type="GLIB_MICRO_VERSION">
<doc xml:space="preserve">The micro version number of the GLib library.

Like #gtk_micro_version, but from the headers used at
Expand Down Expand Up @@ -19313,6 +19313,41 @@ and all memory allocated by the @group is released.</doc>
</parameter>
</parameters>
</callback>
<function-macro name="PASTE" c:identifier="G_PASTE" version="2.20" introspectable="0">
<doc xml:space="preserve">Yields a new preprocessor pasted identifier
@identifier1identifier2 from its expanded
arguments @identifier1 and @identifier2. For example,
the following code:
|[&lt;!-- language="C" --&gt;
#define GET(traveller,method) G_PASTE(traveller_get_, method) (traveller)
const gchar *name = GET (traveller, name);
const gchar *quest = GET (traveller, quest);
GdkColor *favourite = GET (traveller, favourite_colour);
]|

is transformed by the preprocessor into:
|[&lt;!-- language="C" --&gt;
const gchar *name = traveller_get_name (traveller);
const gchar *quest = traveller_get_quest (traveller);
GdkColor *favourite = traveller_get_favourite_colour (traveller);
]|</doc>
<parameters>
<parameter name="identifier1">
<doc xml:space="preserve">an identifier</doc>
</parameter>
<parameter name="identifier2">
<doc xml:space="preserve">an identifier</doc>
</parameter>
</parameters>
</function-macro>
<function-macro name="PASTE_ARGS" c:identifier="G_PASTE_ARGS" introspectable="0">
<parameters>
<parameter name="identifier1">
</parameter>
<parameter name="identifier2">
</parameter>
</parameters>
</function-macro>
<constant name="PDP_ENDIAN" value="3412" c:type="G_PDP_ENDIAN">
<doc xml:space="preserve">Specifies one of the possible types of byte order
(currently unused). See %G_BYTE_ORDER.</doc>
Expand Down Expand Up @@ -25109,6 +25144,43 @@ the #GSource from the main loop.</doc>
<doc xml:space="preserve">The square root of two.</doc>
<type name="gdouble" c:type="gdouble"/>
</constant>
<function-macro name="STATIC_ASSERT" c:identifier="G_STATIC_ASSERT" version="2.20" introspectable="0">
<doc xml:space="preserve">The G_STATIC_ASSERT() macro lets the programmer check
a condition at compile time, the condition needs to
be compile time computable. The macro can be used in
any place where a typedef is valid.

A typedef is generally allowed in exactly the same places that
a variable declaration is allowed. For this reason, you should
not use G_STATIC_ASSERT() in the middle of blocks of code.

The macro should only be used once per source code line.</doc>
<parameters>
<parameter name="expr">
<doc xml:space="preserve">a constant expression</doc>
</parameter>
</parameters>
</function-macro>
<function-macro name="STATIC_ASSERT_EXPR" c:identifier="G_STATIC_ASSERT_EXPR" version="2.30" introspectable="0">
<doc xml:space="preserve">The G_STATIC_ASSERT_EXPR() macro lets the programmer check
a condition at compile time. The condition needs to be
compile time computable.

Unlike G_STATIC_ASSERT(), this macro evaluates to an expression
and, as such, can be used in the middle of other expressions.
Its value should be ignored. This can be accomplished by placing
it as the first argument of a comma expression.

|[&lt;!-- language="C" --&gt;
#define ADD_ONE_TO_INT(x) \
(G_STATIC_ASSERT_EXPR(sizeof (x) == sizeof (int)), ((x) + 1))
]|</doc>
<parameters>
<parameter name="expr">
<doc xml:space="preserve">a constant expression</doc>
</parameter>
</parameters>
</function-macro>
<function-macro name="STRINGIFY" c:identifier="G_STRINGIFY" introspectable="0">
<doc xml:space="preserve">Accepts a macro or a string and converts it into a string after
preprocessor argument expansion. For example, the following code:
Expand Down Expand Up @@ -32306,16 +32378,38 @@ stopped.</doc>
</callback>
<enumeration name="TraverseType" c:type="GTraverseType">
<doc xml:space="preserve">Specifies the type of traversal performed by g_tree_traverse(),
g_node_traverse() and g_node_find(). The different orders are
illustrated here:
g_node_traverse() and g_node_find().

The different orders are illustrated here:

- In order: A, B, C, D, E, F, G, H, I
![](Sorted_binary_tree_inorder.svg)
&lt;picture&gt;
&lt;source srcset="Sorted_binary_tree_inorder-dark.svg"
media="(prefers-color-scheme: dark)"&gt;
&lt;img src="Sorted_binary_tree_inorder.svg"
alt="Sorted binary tree, in-order traversal"&gt;
&lt;/picture&gt;
- Pre order: F, B, A, D, C, E, G, I, H
![](Sorted_binary_tree_preorder.svg)
&lt;picture&gt;
&lt;source srcset="Sorted_binary_tree_preorder-dark.svg"
media="(prefers-color-scheme: dark)"&gt;
&lt;img src="Sorted_binary_tree_preorder.svg"
alt="Sorted binary tree, pre-order traversal"&gt;
&lt;/picture&gt;
- Post order: A, C, E, D, B, H, I, G, F
![](Sorted_binary_tree_postorder.svg)
&lt;picture&gt;
&lt;source srcset="Sorted_binary_tree_postorder-dark.svg"
media="(prefers-color-scheme: dark)"&gt;
&lt;img src="Sorted_binary_tree_postorder.svg"
alt="Sorted binary tree, post-order traversal"&gt;
&lt;/picture&gt;
- Level order: F, B, G, A, D, I, C, E, H
![](Sorted_binary_tree_breadth-first_traversal.svg)</doc>
&lt;picture&gt;
&lt;source srcset="Sorted_binary_tree_breadth-first_traversal-dark.svg"
media="(prefers-color-scheme: dark)"&gt;
&lt;img src="Sorted_binary_tree_breadth-first_traversal.svg"
alt="Sorted binary tree, breadth-first level order traversal"&gt;
&lt;/picture&gt;</doc>
<member name="in_order" value="0" c:identifier="G_IN_ORDER">
<doc xml:space="preserve">vists a node's left child first, then the node itself,
then its right child. This is the one to use if you
Expand Down Expand Up @@ -53520,7 +53614,7 @@ the Single Unix Specification.</doc>
</parameter>
</parameters>
</function>
<function name="sort_array" c:identifier="g_sort_array" introspectable="0">
<function name="sort_array" c:identifier="g_sort_array" version="2.82" introspectable="0">
<doc xml:space="preserve">This is just like the standard C [`qsort()`](man:qsort(3)) function, but
the comparison routine accepts a user data argument
(like [`qsort_r()`](man:qsort_r(3))).
Expand Down
2 changes: 1 addition & 1 deletion Gdk-3.0.gir
Original file line number Diff line number Diff line change
Expand Up @@ -14773,7 +14773,7 @@ See gdk_keymap_get_caps_lock_state().</doc>
<constant name="MAX_TIMECOORD_AXES" value="128" c:type="GDK_MAX_TIMECOORD_AXES">
<type name="gint" c:type="gint"/>
</constant>
<constant name="MICRO_VERSION" value="42" c:type="GDK_MICRO_VERSION">
<constant name="MICRO_VERSION" value="44" c:type="GDK_MICRO_VERSION">
<type name="gint" c:type="gint"/>
</constant>
<constant name="MINOR_VERSION" value="24" c:type="GDK_MINOR_VERSION">
Expand Down
Loading

0 comments on commit 39dac97

Please sign in to comment.