Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

vf_get_prop_value(3) [debian man page]

vf_get_prop_value(3)					     Library Functions Manual					      vf_get_prop_value(3)

NAME
vf_get_prop_value - vf_get_prop_value() SYNOPSIS
#include <../vformat/vf_iface.h> extern bool_t vf_get_prop_value ( VF_PROP_T *p_prop, void **pp_value, uint32_t *p_size, vf_encoding_t *p_encoding ); PARAMETERS
VF_PROP_T *p_prop The property. void **pp_value Pointer value. uint32_t *p_size Integer value. vf_encoding_t *p_encoding Type of return values. DESCRIPTION
Get hold of raw fields associated with the property. These are of various types: VF_ENC_VOBJECT - *Pp_value = pointer to contained VF_OBJECT_T which can be passed back to any of the object manipulation functions. VF_ENC_7BIT, VF_ENC_QUOTEDPRINTABLE - *Pp_value = ptr to array of char*, *p_size = number of elts. VF_ENC_8BIT, VF_BASE64 - *Pp_value = ptr to bytes, *p_size = number of bytes. RETURNS
TRUE <=> encoding is valid, FALSE else. SEE ALSO
vf_parse_init(3), vf_parse_text(3), vf_parse_end(3), vf_read_file(3), vf_write_file(3), vf_get_next_object(3), vf_create_object(3), vf_get_object_type(3), vf_get_property(3), vf_get_property_ex(3), vf_get_next_property(3), vf_set_prop_value(3), vf_get_prop_value_string(3), vf_get_prop_name_string(3), vf_set_prop_name_string(3), vf_get_prop_name(3), vf_get_prop_value_object(3), vf_set_prop_value_object(3), vf_set_prop_value_string(3), vf_set_prop_value_base64(3), vf_get_prop_value_base64(3), vf_set_prop- erty_from_file(3), vf_delete_object(3), vf_delete_prop(3), vf_find_prop_qual_index(3), vf_is_modified(3), vf_find_charset(3), vf_date_string_to_time(3), vf_period_string_to_time(3), vf_period_time_to_string(3), vf_set_prop_value_time(3), vf_get_prop_value_time(3) c2man vf_iface.h 30 April 2003 vf_get_prop_value(3)

Check Out this Related Man Page

ATOMIC_CAS(3)						   BSD Library Functions Manual 					     ATOMIC_CAS(3)

NAME
atomic_cas, atomic_cas_32, atomic_cas_uint, atomic_cas_ulong, atomic_cas_ptr, atomic_cas_64, atomic_cas_32_ni, atomic_cas_uint_ni, atomic_cas_ulong_ni, atomic_cas_ptr_ni, atomic_cas_64_ni -- atomic compare-and-swap operations SYNOPSIS
#include <sys/atomic.h> uint32_t atomic_cas_32(volatile uint32_t *ptr, uint32_t old, uint32_t new); unsigned int atomic_cas_uint(volatile unsigned int *ptr, unsigned int old, unsigned int new); unsigned long atomic_cas_ulong(volatile unsigned long *ptr, unsigned long old, unsigned long new); void * atomic_cas_ptr(volatile void *ptr, void *old, void *new); uint64_t atomic_cas_64(volatile uint64_t *ptr, uint64_t old, uint64_t new); uint32_t atomic_cas_32_ni(volatile uint32_t *ptr, uint32_t old, uint32_t new); unsigned int atomic_cas_uint_ni(volatile unsigned int *ptr, unsigned int old, unsigned int new); unsigned long atomic_cas_ulong_ni(volatile unsigned long *ptr, unsigned long old, unsigned long new); void * atomic_cas_ptr_ni(volatile void *ptr, void *old, void *new); uint64_t atomic_cas_64_ni(volatile uint64_t *ptr, uint64_t old, uint64_t new); DESCRIPTION
The atomic_cas family of functions perform a compare-and-swap operation in an atomic fashion. The value of the variable referenced by ptr is compared against old. If the values are equal, new is stored in the variable referenced by ptr. The old value of the variable referenced by ptr is always returned regardless of whether or not the new value was stored. Applications can test for success of the operation by comparing the return value to the value passed as old; if they are equal then the new value was stored. The non-interlocked variants, *_ni(), guarantee atomicity within the same CPU with respect to interrupts and preemption. For example, they are suitable for synchronizing compare-and-swap operations on a variable shared by a thread and an interrupt that are bound to the same CPU. The *_ni() variants are not atomic with respect to different CPUs. *_ni() variants should avoid the interprocessor synchronization overhead of the standard compare-and-swap operations. The 64-bit variants of these functions are available only on platforms that can support atomic 64-bit memory access. Applications can check for the availability of 64-bit atomic memory operations by testing if the pre-processor macro __HAVE_ATOMIC64_OPS is defined. SEE ALSO
atomic_ops(3) HISTORY
The atomic_cas functions first appeared in NetBSD 5.0. NOTES
On some architectures, a *_ni() variant is merely an alias for the corresponding standard compare-and-swap operation. While the non-inter- locked variant behaves correctly on those architectures, it does not avoid the interprocessor synchronization overhead. BSD
February 11, 2010 BSD
Man Page