File: pipe.yo

package info (click to toggle)
bobcat 6.02.02-1
  • links: PTS, VCS
  • area: main
  • in suites: bookworm
  • size: 13,960 kB
  • sloc: cpp: 18,954; fortran: 5,617; makefile: 2,787; sh: 659; perl: 401; ansic: 26
file content (232 lines) | stat: -rw-r--r-- 8,613 bytes parent folder | download
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
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
includefile(include/header)

COMMENT(manpage, section, releasedate, archive, short name)
manpage(FBB::Pipe)(3bobcat)(_CurYrs_)(libbobcat-dev__CurVers_)
                    (System Level Communication Pipe)

manpagename(FBB::Pipe)(Defines a system level communication pipe)

manpagesynopsis()
    bf(#include <bobcat/pipe>)nl()
    Linking option: tt(-lbobcat)

manpagedescription()
    bf(FBB::Pipe) objects may be used to construct a em(pipe). tt(Pipe)
objects offer a simple interface to the reading and writing ends of
pipes. tt(Pipe) objects are object-wrappers around the bf(pipe)(2) system
call.

    A tt(Pipe) which is created just before a program forks can be used to set
up a line of communication between the parent and child process. Information
which is written by the child process to its standard output stream can be
redirected to the writing end of the pipe (using the tt(writtenBy)
member). The information appearing at the reading end of the pipe can then be
extracted using, e.g., an tt(IFdStream) object, initialized with the
tt(Pipe)'s reading file descriptor, or the reading end of the pipe can be
redirected to an existing stream whose file descriptor is known, like tt(cin)
(which uses the tt(STDIN_FILENO) file descriptor).

    When a tt(Pipe) object goes out of scope, no bf(close)(2) operation is
performed on the pipe's file descriptors. After setting up the pipe using the
tt(Pipe's) member functions and passing the tt(Pipe's) file descriptors to
code that uses the tt(Pipe's) descriptors, the tt(Pipe) object might even be
destroyed. The using code is responsible for closing the pipe. If the pipe
should be closed at destruction time, then a class could be derived from
bf(Pipe)(3bobcat), whose destructor may then close the pipe. Alternatively,
tt(Pope's close) member can be called.

    The value -1 indicates that a file descriptor does not refer to a
bf(pipe)(2) file descriptor.

includefile(include/namespace)

manpagesection(INHERITS FROM)
    -

manpagesection(CONSTRUCTORS)
    itemization(
    itb(Pipe())
        The default tt(Pipe) constructor constructs a pipe, calling
bf(pipe)(2).

    This constructor throws an tt(Exception) exception if the default tt(Pipe)
constructor did not properly complete.  The thrown bf(Exception) object's
tt(which()) member shows the system's tt(errno) value set by the failing
bf(pipe)(2) function.

    itb(Pipe(Pipe &&tmp))
        The move constructor moves the temporary object's file descriptors to
the tt(Pipe) object being constructed.

    itb(Pipe(int const *fd))
        This constructor expects two file descriptors, referring to the read
and write file descriptors as returned by bf(pipe)(2).

    itb(Pipe(bool initialize))
        This constructor can be used when the tt(Pipe) object should not be
associated with an existing pipe. Instead it initializes its read and write
file descriptors to -1. This constructor may be used in classes that define
tt(Pipe) data members that only after the object is constructed can open their
pipes. Having constructing a tt(Pipe obj(false)) object it can be associated
with an open pipe using tt(obj = Pipe{}). When passing the argument tt(true)
it calls tt(Pipe()) to construct a pipe.
    )

    The move constructor and move assignment operator are available. Copy
construction and copy assignment are not defined.

    Note that tt(Pipe's) destructor does not close the pipe's file
descriptors. To close the pipes tt(close) must be called.

manpagesection(MEMBER FUNCTIONS)

    itemization(
    itb(void close())
        Both file descriptors of the tt(Pipe) object are closed;

    itb(void closeReadFd())
        The file descriptor of the tt(Pipe) object that is associated with the
reading end of the pipe is closed;

    itb(void closeWriteFd())
        The file descriptor of the tt(Pipe) object that is associated with the
writing end of the pipe is closed;

    itb(int readFd() const)
        Returns the pipe's file descriptor that is used for reading

    itb(void readFrom(int filedescriptor))
        Sets up redirection from the internal em(read) filedescriptor to the
given filedescriptor: information written to the write-end of the pipe may be
retrieved by extracting the information from the stream that is associated
with the indicated file descriptor. E.g., after the call
tt(readFrom(STDIN_FILENO)) information  inserted into the
write-end of the pipe can be retrieved from tt(cin).

    itb(void readFrom(int const *filedescriptors, size_t n))
        Sets up redirection from the internal em(read) filedescriptor to the
given filedescriptors: information is read from the tt(Pipe) object when
reading from any of the bf(n) provided filedescriptors (experimental).

    itb(int readOnly())
        Closes the writing end of the pipe, returns the reading end's file
descriptor. This member can be used, e.g., to construct an tt(IFdStream)
object to extract the information that is inserted into the write-end of the
pipe.

    itb(void swap(Pipe &other))
        The current and other tt(Pipe) objects are swapped. Following this
call the current tt(Pipe) objects refer to the other object's pipe file
descriptors and vice versa.

    itb(int writeFd() const)
        Returns the pipe's file descriptor that is used for writing.

    itb(void writtenBy(int filedescriptor))
        Sets up redirection from the internal em(write) filedescriptor to the
given filedescriptor: information is  written to the tt(Pipe) object when
writing to the provided filedescriptor. E.g., after the call
tt(writtenBy(STDOUT_FILENO)) information sent to the standard output stream (by
either tt(cout) or by a child process (cf. bf(exec)(3))) is inserted into the
write-end of the pipe.

    itb(void writtenBy(int const *filedescriptors, size_t n))
        Sets up redirection from the internal em(write) filedescriptor to the
given filedescriptors: information is inserted into the write-end of the
tt(Pipe) object when writing to each of the bf(n) provided filedescriptors.
E.g., when passing an array of two tt(int) values, respectively equal to
tt(STDOUT_FILENO) and tt(STDERR_FILENO) to this member, all information which
is thereafter sent to the standard output or error streams is inserted into
the write-end of the pipe.

    itb(int writeOnly())
        Closes the reading end of the pipe, returns the writing end's file
descriptor.
    )

manpagesection(PROTECTED ENUMERATION)
    The bf(RW) protected enumeration has the following elements:

    itemization(
    itb(READ)
        The index in bf(d_fd[]) (see below) of the element holding the pipe's
reading file descriptor;

    itb(WRITE)
        The index in bf(d_fd[]) (see below) of the element holding the pipe's
writing file descriptor
    )

manpagesection(PROTECTED MEMBER FUNCTION)

    itemization(
    itb(void close(RW rw))
        When passing argument RW::READ to this member the reading end of the
tt(Pipe) object's pipe is closed. When passing argument RW::WRITE the writing
end of the tt(Pipe) object's pipe is closed.
    )


manpagesection(EXAMPLE)
        verb(
    #include <bobcat/pipe>
    #include <sys/types.h>
    #include <sys/wait.h>
    #include <unistd.h>
    #include <iostream>
    #include <string>

    using namespace std;
    using namespace FBB;

    int main()
    {
        Pipe p;                         // construct a pipe

        cout << "Read file descriptor: " << p.readFd() << "\n"
                "Write file descriptor: " << p.writeFd() << endl;

        int pid = fork();

        if (pid == -1)
            return 1;

        if (!pid)                       //child
        {
            p.readFrom(STDIN_FILENO);   // read what goes into the pipe

            string s;

            getline(cin, s);
            cout << "CHILD: Got `" << s << "'\n";

            getline(cin, s);
            cout << "CHILD: Got `" << s << "'\n";

            return 0;
        }

        p.writtenBy(STDOUT_FILENO);      // write to the pipe via cout

        cout << "first line" << "\n"
                "second line" << '\n';

        waitpid(pid, 0, 0);
    }
        )

    See also the 2nd example at bf(fork)(3bobcat)

manpagefiles()
    em(bobcat/pipe) - defines the class interface

manpageseealso()
    bf(bobcat)(7), bf(fork)(3bobcat), bf(pipe)(2), bf(mkfifo)(3)

manpagebugs()
    Note that when the pipe goes out of scope, no bf(close)(2) operation is
performed on the pipe's ends. If the pipe should be closed by the desctructor,
derive a class from bf(Pipe)(3bobcat), whose destructor performs the required
closing-operation.

includefile(include/trailer)