Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

ne_buffer(3) [opensolaris man page]

NE_BUFFER(3)							neon API reference						      NE_BUFFER(3)

NAME
ne_buffer - string buffer handling SYNOPSIS
#include <ne_string.h> typedef struct { char *data; size_t used; size_t length; } ne_buffer; DESCRIPTION
The ne_buffer type represents an expandable memory buffer for holding NUL-terminated strings. The data field points to the beginnning of the string, the length of which is given by the used field. The current size of memory allocated is given by the length field. It is not recommended that the fields of a buffer are manipulated directly. The data pointer may change when the buffer is modified. A buffer is created using ne_buffer_create(3) or ne_buffer_ncreate(3), and destroyed using ne_buffer_destroy(3) or ne_buffer_finish(3). The functions ne_buffer_append(3), ne_buffer_zappend(3) and ne_buffer_concat(3) are used to append data to a buffer. If the string referenced by the data pointer is modified directly (rather than using one of the functions listed above), ne_buffer_altered must be called. AUTHOR
Joe Orton <neon@webdav.org>. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +--------------------+-----------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +--------------------+-----------------+ |Availability | SUNWneon | +--------------------+-----------------+ |Interface Stability | Volatile | +--------------------+-----------------+ NOTES
Source for Neon is available on http://opensolaris.org. neon 0.25.5 20 January 2006 NE_BUFFER(3)

Check Out this Related Man Page

NE_BUFFER_CLEAR(3)						neon API reference						NE_BUFFER_CLEAR(3)

NAME
ne_buffer_clear, ne_buffer_grow, ne_buffer_altered - general purpose of group of functions SYNOPSIS
#include <ne_string.h> void ne_buffer_clear (ne_buffer *buf); void ne_buffer_altered (ne_buffer *buf); void ne_buffer_grow (ne_buffer *buf, size_t size); DESCRIPTION
The ne_buffer_clear function sets the string stored in buf to be the empty string (""). The ne_buffer_altered function must be used after the string stored in the buffer buf is modified by directly rather than using ne_buf- fer_append(3), ne_buffer_zappend(3) or ne_buffer_concat(3). The ne_buffer_grow function ensures that at least size bytes are allocated for the string; this can be used if a large amount of data is going to be appended to the buffer and may result in more efficient memory allocation. AUTHOR
Joe Orton <neon@webdav.org>. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +--------------------+-----------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +--------------------+-----------------+ |Availability | SUNWneon | +--------------------+-----------------+ |Interface Stability | Volatile | +--------------------+-----------------+ NOTES
Source for Neon is available on http://opensolaris.org. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +--------------------+-----------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +--------------------+-----------------+ |Availability | SUNWneon | +--------------------+-----------------+ |Interface Stability | Volatile | +--------------------+-----------------+ NOTES
Source for Neon is available on http://opensolaris.org. neon 0.25.5 20 January 2006 NE_BUFFER_CLEAR(3)
Man Page

4 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Command line buffer limit?

Is there a limit (255 chars?) on the command line?? I'm trying to copy some generated java & class files from one dir to another and ID the old & new versions by: find . -name FFSFIXADminCallbackBean.java I then do a copy and paste of the source and target - $ cp -p source target It... (7 Replies)
Discussion started by: kornshellmaven
7 Replies

2. UNIX for Advanced & Expert Users

Discussion on buffering of standard I/O library

Hi, There are three type of buffering: Fully buffered,line buffered,and unbuffered. The goal of the buffering provided by the standard I/O library is to use the minimum number of read and write calls. I understand that decrease write() calls when use output function output data to a file ,... (4 Replies)
Discussion started by: Edward114
4 Replies

3. Programming

Why must flush all line-buffered output streams?

Hi, Mentioned in Stevens & Rago "Advanced Programming in the UNIX" I don't understand why must flush all line-buffered output streams when (a)an unbuffered or (b)a line-buffered stream require data from kernel? (2 Replies)
Discussion started by: Edward114
2 Replies

4. Shell Programming and Scripting

Getting piped input from a program that's buffering it's stdout

The old buffering problem again, in a very specific case. On FreeBSD this time, but it's the generic line-buffered vs fully-buffered problem. I'm trying to pick an available bluetooth speaker (all named audio_N), by pinging all of them en mass and taking the first to respond. The... (10 Replies)
Discussion started by: Juha Nurmela
10 Replies