blob: 1e07c3c3aff156d3f2ff0da92cd8d9ea47f4d97f (
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
|
xs_msg_init_size(3)
===================
NAME
----
xs_msg_init_size - initialise Crossroads message of a specified size
SYNOPSIS
--------
*int xs_msg_init_size (xs_msg_t '*msg', size_t 'size');*
DESCRIPTION
-----------
The _xs_msg_init_size()_ function shall allocate any resources required to
store a message 'size' bytes long and initialise the message object referenced
by 'msg' to represent the newly allocated message.
The implementation shall choose whether to store message content on the stack
(small messages) or on the heap (large messages). For performance reasons
_xs_msg_init_size()_ shall not clear the message data.
CAUTION: Never access 'xs_msg_t' members directly, instead always use the
_xs_msg_ family of functions.
CAUTION: The functions _xs_msg_init()_, _xs_msg_init_data()_ and
_xs_msg_init_size()_ are mutually exclusive. Never initialize the same
'xs_msg_t' twice.
RETURN VALUE
------------
The _xs_msg_init_size()_ function shall return zero if successful. Otherwise
it shall return `-1` and set 'errno' to one of the values defined below.
ERRORS
------
*ENOMEM*::
Insufficient storage space is available.
SEE ALSO
--------
linkxs:xs_msg_init_data[3]
linkxs:xs_msg_init[3]
linkxs:xs_msg_close[3]
linkxs:xs_msg_data[3]
linkxs:xs_msg_size[3]
linkxs:xs[7]
AUTHORS
-------
The Crossroads documentation was written by Martin Sustrik <sustrik@250bpm.com>
and Martin Lucina <martin@lucina.net>.
|
