blob: 657304379e895968a42c7f770b8cc7c09047efcc (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
|
<?xml version="1.0"?>
<page id="Regress.annotation_custom_destroy"
type="topic"
style="function"
xmlns="http://projectmallard.org/1.0/"
xmlns:api="http://projectmallard.org/experimental/api/"
xmlns:ui="http://projectmallard.org/1.0/ui/">
<info>
<link type="guide" xref="index" group="function"/>
<api:function>
<api:returns>
<api:type>void</api:type>
</api:returns>
<api:name>regress_annotation_custom_destroy</api:name>
<api:arg>
<api:type>RegressAnnotationCallback</api:type>
<api:name>callback</api:name>
</api:arg>
<api:arg>
<api:type>RegressAnnotationNotifyFunc</api:type>
<api:name>destroy</api:name>
</api:arg>
<api:arg>
<api:type>gpointer</api:type>
<api:name>data</api:name>
</api:arg>
</api:function>
</info>
<title>regress_annotation_custom_destroy</title>
<synopsis><code mime="text/x-csrc">
void regress_annotation_custom_destroy (RegressAnnotationCallback callback,
RegressAnnotationNotifyFunc destroy,
gpointer data);
</code></synopsis>
<p>Test messing up the heuristic of closure/destroy-notification
detection, and fixing it via regress_annotations.</p>
<terms>
<item>
<title><code>callback</code></title>
<p>Destroy notification</p>
</item>
<item>
<title><code>destroy</code></title>
</item>
<item>
<title><code>data</code></title>
</item>
<item>
<title><code>Returns</code></title>
</item>
</terms>
</page>
|
