udi_instance_attr_type_t(3udi)

---

Instance attribute data-type type

SYNOPSIS

#include <udi.h>

typedef udi_ubit8_t udi_instance_attr_type_t;
 
/* Instance Attribute Types */
 

#define  UDI_ATTR_NONE				0
 
#define  UDI_ATTR_STRING				1
 
#define  UDI_ATTR_ARRAY8				2
 
#define  UDI_ATTR_UBIT32				3
 
#define  UDI_ATTR_BOOLEAN				4
 
#define  UDI_ATTR_FILE				5
 

DESCRIPTION This type is used to identify the data type of an instance attribute. Instance attribute data types determine the storage requirements, encodings, and semantics of instance attribute values.

A list of supported instance attribute data type codes is given below, along with a description of each attribute.

UDI_ATTR_NONE indicates that an attribute has no current value. This type is only legal with an attribute length of zero.

UDI_ATTR_STRING identifies a null-terminated character string, consisting of Unicode characters encoded with the UTF-8 byte-stream character encoding. This encoding ensures that any byte in the string that has the 8th bit clear is in fact an ASCII character and not part of a multi-byte character. The null-terminator byte is considered part of the attribute value and is required.

UDI_ATTR_ARRAY8 identifies a sequence of udi_ubit8_t values.

UDI_ATTR_UBIT32 identifies a single udi_ubit32_t value. The attribute length for attributes of this type must be exactly sizeof(udi_ubit32_t).

UDI_ATTR_BOOLEAN identifies a single udi_boolean_t value. The attribute length for attributes of this type must be exactly sizeof(udi_boolean_t).

UDI_ATTR_FILE identifies a read-only attribute whose value is contained in a driver-provided external file. The attribute name must match a "readable_file" entry in the driver's persistent configuration information, optionally suffixed with a colon (`:') followed by ASCII digits representing a decimal integer up to 224-1. The suffix indicates the beginning file offset to read from; zero is the default. If this offset suffix is provided, it does not count as part of the actual attribute name, so does not have to fit within the 63-character limit.