NE_BUFFER_CREATE(3) neon API reference NE_BUFFER_CREATE(3)NAME
ne_buffer_create, ne_buffer_ncreate - general purpose of group of functions
SYNOPSIS
#include <ne_alloc.h>
ne_buffer *ne_buffer_create (void);
ne_buffer *ne_buffer_ncreate (size_t size);
DESCRIPTION
ne_buffer_create creates a new buffer object, with an implementation-defined initial size. ne_buffer_ncreate creates an ne_buffer where the
minimum initial size is given in the size parameter. The buffer created will contain the empty string ("").
RETURN VALUE
Both functions return a pointer to a new buffer object, and never NULL.
SEE ALSO ne_buffer(3)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_CREATE(3)
Check Out this Related 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)
i am looking forward to this one:
http://www.opensolaris.org/jive/message.jspa?messageID=11672#11672
i thought that the gentoo community would release the first opensolaris distri, but perhabs we will get a chance to try opensolaris within 1/2 hour installation and not 12 hours "gentoo-stage_1"... (2 Replies)
Hi all,
I have two virtual machines, one with Suse and another with opensolaris 2009.06.
The ldap server is in the Suse machine.
From my opensolaris, with command ldalist i can see the information about the ldap configuration, i mean, the dn: ou:....
if i type id <ldapuser> i can see the user... (0 Replies)