1a2,4
> .\" Copyright (c) 2004-2005
> .\" Hartmut Brandt.
> .\" All rights reserved.
29c32
< .\" $Begemot: libunimsg/man/unimsg.3,v 1.3 2005/05/23 12:00:09 brandt_h Exp $
---
> .\" $Begemot: libunimsg/man/unimsg.3,v 1.4 2005/06/15 11:37:10 brandt_h Exp $
31c34
< .Dd May 23, 2005
---
> .Dd June 14, 2005
90c93,94
< These functions are used to manipulate variable sized message. They are
---
> These functions are used to manipulate variable sized message.
> They are
92,93c96,97
< signalling generally is a low bandwidth task. All the functions operation on
< a
---
> signalling generally is a low bandwidth task.
> All the functions operation on a
110c114,115
< points just to the first byte behind that buffer. This buffer is allocated
---
> points just to the first byte behind that buffer.
> This buffer is allocated
127,128c132,133
< returns the actual size of the message (the number of used bytes). The
< macro
---
> returns the actual size of the message (the number of used bytes).
> The macro
143,145c148,150
< bytes (In fact it allocates a couple of bytes more). If the allocation fails
< NULL is returned. The pointers are setup so that there is no leading space
< in the buffer.
---
> bytes (In fact it allocates a couple of bytes more).
> If the allocation fails NULL is returned.
> The pointers are setup so that there is no leading space in the buffer.
148,149c153,154
< constructs a new message from a variable number of buffers. The arguments
< are pairs of
---
> constructs a new message from a variable number of buffers.
> The arguments are pairs of
153,156c158,162
< buffer sizes, terminated by a NULL pointer. The function computes the total
< resulting message size, allocates a message and copies all the buffers
< into the message. The message is built to have no leading space. If the
< allocation fails, NULL is returned.
---
> buffer sizes, terminated by a NULL pointer.
> The function computes the total resulting message size, allocates a message
> and copies all the buffers into the message.
> The message is built to have no leading space.
> If the allocation fails, NULL is returned.
172,174c178,182
< additional byte at the end. The leading space does not change. This function
< may reallocate the message buffer. The function returns 0 on success and ENOMEM
< if the reallocation fails. In this case the message buffer is not changed.
---
> additional byte at the end.
> The leading space does not change.
> This function may reallocate the message buffer.
> The function returns 0 on success and ENOMEM if the reallocation fails.
> In this case the message buffer is not changed.
179c187,188
< bytes. If not it calls
---
> bytes.
> If not it calls
181c190,191
< to make the message buffer larger. The macro returns 0 on success or ENOMEM
---
> to make the message buffer larger.
> The macro returns 0 on success or ENOMEM
197c207,208
< needs not to be aligned). All three functions call
---
> needs not to be aligned).
> All three functions call
199,201c210,213
< to make sure, that the buffer contents fit into the message. They
< return 0 on success and ENOMEM if the buffer is too small and the reallocation
< fails. In this case the message buffer is not changed.
---
> to make sure, that the buffer contents fit into the message.
> They return 0 on success and ENOMEM if the buffer is too small and
> the reallocation fails.
> In this case the message buffer is not changed.
207c219,220
< be in network byte order. It adjusts
---
> be in network byte order.
> It adjusts
215c228,229
< be in network byte order. It adjusts
---
> be in network byte order.
> It adjusts
224,225c238,240
< 32-bit integer from the buffer counted from the end of the buffer. The
< integer is assumed to be in network byte order. A value of -1 for
---
> 32-bit integer from the buffer counted from the end of the buffer.
> The integer is assumed to be in network byte order.
> A value of -1 for
228,229c243,244
< just before the last four bytes and so on. All three functions do not check
< that the message is large enough.
---
> just before the last four bytes and so on.
> All three functions do not check that the message is large enough.
> .\" Copyright (c) 2004-2005
> .\" Hartmut Brandt.
> .\" All rights reserved.
29c32
< .\" $Begemot: libunimsg/man/unimsg.3,v 1.3 2005/05/23 12:00:09 brandt_h Exp $
---
> .\" $Begemot: libunimsg/man/unimsg.3,v 1.4 2005/06/15 11:37:10 brandt_h Exp $
31c34
< .Dd May 23, 2005
---
> .Dd June 14, 2005
90c93,94
< These functions are used to manipulate variable sized message. They are
---
> These functions are used to manipulate variable sized message.
> They are
92,93c96,97
< signalling generally is a low bandwidth task. All the functions operation on
< a
---
> signalling generally is a low bandwidth task.
> All the functions operation on a
110c114,115
< points just to the first byte behind that buffer. This buffer is allocated
---
> points just to the first byte behind that buffer.
> This buffer is allocated
127,128c132,133
< returns the actual size of the message (the number of used bytes). The
< macro
---
> returns the actual size of the message (the number of used bytes).
> The macro
143,145c148,150
< bytes (In fact it allocates a couple of bytes more). If the allocation fails
< NULL is returned. The pointers are setup so that there is no leading space
< in the buffer.
---
> bytes (In fact it allocates a couple of bytes more).
> If the allocation fails NULL is returned.
> The pointers are setup so that there is no leading space in the buffer.
148,149c153,154
< constructs a new message from a variable number of buffers. The arguments
< are pairs of
---
> constructs a new message from a variable number of buffers.
> The arguments are pairs of
153,156c158,162
< buffer sizes, terminated by a NULL pointer. The function computes the total
< resulting message size, allocates a message and copies all the buffers
< into the message. The message is built to have no leading space. If the
< allocation fails, NULL is returned.
---
> buffer sizes, terminated by a NULL pointer.
> The function computes the total resulting message size, allocates a message
> and copies all the buffers into the message.
> The message is built to have no leading space.
> If the allocation fails, NULL is returned.
172,174c178,182
< additional byte at the end. The leading space does not change. This function
< may reallocate the message buffer. The function returns 0 on success and ENOMEM
< if the reallocation fails. In this case the message buffer is not changed.
---
> additional byte at the end.
> The leading space does not change.
> This function may reallocate the message buffer.
> The function returns 0 on success and ENOMEM if the reallocation fails.
> In this case the message buffer is not changed.
179c187,188
< bytes. If not it calls
---
> bytes.
> If not it calls
181c190,191
< to make the message buffer larger. The macro returns 0 on success or ENOMEM
---
> to make the message buffer larger.
> The macro returns 0 on success or ENOMEM
197c207,208
< needs not to be aligned). All three functions call
---
> needs not to be aligned).
> All three functions call
199,201c210,213
< to make sure, that the buffer contents fit into the message. They
< return 0 on success and ENOMEM if the buffer is too small and the reallocation
< fails. In this case the message buffer is not changed.
---
> to make sure, that the buffer contents fit into the message.
> They return 0 on success and ENOMEM if the buffer is too small and
> the reallocation fails.
> In this case the message buffer is not changed.
207c219,220
< be in network byte order. It adjusts
---
> be in network byte order.
> It adjusts
215c228,229
< be in network byte order. It adjusts
---
> be in network byte order.
> It adjusts
224,225c238,240
< 32-bit integer from the buffer counted from the end of the buffer. The
< integer is assumed to be in network byte order. A value of -1 for
---
> 32-bit integer from the buffer counted from the end of the buffer.
> The integer is assumed to be in network byte order.
> A value of -1 for
228,229c243,244
< just before the last four bytes and so on. All three functions do not check
< that the message is large enough.
---
> just before the last four bytes and so on.
> All three functions do not check that the message is large enough.