File: gimpsignal.xml

package info (click to toggle)
gimp 2.2.13-1etch4
  • links: PTS
  • area: main
  • in suites: etch
  • size: 94,832 kB
  • ctags: 47,113
  • sloc: ansic: 524,858; xml: 36,798; lisp: 9,870; sh: 9,409; makefile: 7,923; python: 2,674; perl: 2,589; yacc: 520; lex: 334
file content (116 lines) | stat: -rw-r--r-- 4,838 bytes parent folder | download | duplicates (2)
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
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN" 
               "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd">

<refentry id="libgimpbase-gimpsignal">
<refmeta>
<refentrytitle role="top_of_page">gimpsignal</refentrytitle>
<manvolnum>3</manvolnum>
<refmiscinfo>LIBGIMPBASE Library</refmiscinfo>
</refmeta>

<refnamediv>
<refname>gimpsignal</refname>
<refpurpose>Portable signal handling.</refpurpose>
<!--[<xref linkend="desc" endterm="desc.title"/>]-->
</refnamediv>

<refsynopsisdiv role="synopsis">
<title role="synopsis.title">Synopsis</title>

<synopsis>



<link linkend="void">void</link>        (<link linkend="GimpSignalHandlerFunc">*GimpSignalHandlerFunc</link>)        (<link linkend="gint">gint</link> signum);
<link linkend="GimpSignalHandlerFunc">GimpSignalHandlerFunc</link> <link linkend="gimp-signal-private">gimp_signal_private</link>   (<link linkend="gint">gint</link> signum,
                                             <link linkend="GimpSignalHandlerFunc">GimpSignalHandlerFunc</link> handler,
                                             <link linkend="gint">gint</link> flags);
</synopsis>
</refsynopsisdiv>









<refsect1 role="desc">
<title role="desc.title">Description</title>
<para>
Portable signal handling.

</para>
</refsect1>

<refsect1 role="details">
<title role="details.title">Details</title>
<refsect2>
<title><anchor id="GimpSignalHandlerFunc" role="function"/>GimpSignalHandlerFunc ()</title>
<indexterm><primary>GimpSignalHandlerFunc</primary></indexterm><programlisting><link linkend="void">void</link>        (*GimpSignalHandlerFunc)        (<link linkend="gint">gint</link> signum);</programlisting>
<para>
A prototype for signal handler functions. Note that each function which
takes or returns a variable of this type also accepts or may return
special values defined by your system's signal.h header file (like
<parameter>SIG_DFL</parameter> or <parameter>SIG_IGN</parameter>).
</para><variablelist role="params">
<varlistentry><term><parameter>signum</parameter>&nbsp;:</term>
<listitem><simpara>The number of the signal. Useful if different signals are handled
         by a single handler.


</simpara></listitem></varlistentry>
</variablelist></refsect2>
<refsect2>
<title><anchor id="gimp-signal-private" role="function"/>gimp_signal_private ()</title>
<indexterm><primary>gimp_signal_private</primary></indexterm><programlisting><link linkend="GimpSignalHandlerFunc">GimpSignalHandlerFunc</link> gimp_signal_private   (<link linkend="gint">gint</link> signum,
                                             <link linkend="GimpSignalHandlerFunc">GimpSignalHandlerFunc</link> handler,
                                             <link linkend="gint">gint</link> flags);</programlisting>
<para>
This function furnishes a workalike for signal(2) but
which internally invokes sigaction(2) after certain
sa_flags are set; these primarily to ensure restarting
of interrupted system calls. See sigaction(2)  It is a
aid to transition and not new development: that effort
should employ sigaction directly. [gosgood 18.04.2000]
</para>
<para>
Cause <parameter>handler</parameter> to be run when <parameter>signum</parameter> is delivered.  We
use sigaction(2) rather than signal(2) so that we can control the
signal handler's environment completely via <parameter>flags</parameter>: some signal(2)
implementations differ in their sematics, so we need to nail down
exactly what we want. [austin 06.04.2000]</para>
<para>

</para><variablelist role="params">
<varlistentry><term><parameter>signum</parameter>&nbsp;:</term>
<listitem><simpara> Selects signal to be handled see man 5 signal (or man 7 signal)
</simpara></listitem></varlistentry>
<varlistentry><term><parameter>handler</parameter>&nbsp;:</term>
<listitem><simpara> Handler that maps to signum. Invoked by O/S.
          Handler gets signal that caused invocation. Corresponds
          to the <parameter>sa_handler</parameter> field of the <parameter>sigaction</parameter> struct.
</simpara></listitem></varlistentry>
<varlistentry><term><parameter>flags</parameter>&nbsp;:</term>
<listitem><simpara> Preferences. OR'ed SA_&lt;xxx&gt;. See man sigaction. Corresponds
        to the <parameter>sa_flags</parameter> field of the <parameter>sigaction</parameter> struct.
</simpara></listitem></varlistentry>
<varlistentry><term><emphasis>Returns</emphasis>&nbsp;:</term><listitem><simpara> A reference to the signal handling function which was
         active before the call to <link linkend="gimp-signal-private"><function>gimp_signal_private()</function></link>.
</simpara></listitem></varlistentry>
</variablelist></refsect2>

</refsect1>



<refsect1>
<title>See Also</title>
<para>
signal(2), signal(5 or 7), sigaction(2).
</para>
</refsect1>

</refentry>