yumapro  20.10-12
YumaPro SDK

one value to match one type More...

#include <val.h>

Collaboration diagram for val_value_t_:

Data Structures

union  v_
 union of all the NCX-specific sub-types note that the following invisible constructs should never show up in this struct: More...
 

Data Fields

dlq_hdr_t qhdr
 queue header to insert in dlq_hdr list
 
struct obj_template_t_obj
 common fields More...
 
typ_def_t * typdef
 bptr to typdef if leaf
 
const xmlChar * name
 back pointer to elname
the dname field is moved to val_extra_t and only used when the value is constructed from dummy objects or no objects at all
 
struct val_value_t_parent
 back-ptr to parent if any
 
struct val_child_hdr_t_hdr
 back-ptr to own child_hdr
 
val_extra_t * val_extra
 val extra fields only needed about 25% of the time
 
uint32 flags
 internal status flags
 
xmlns_id_t nsid
 namespace ID for this node
 
ncx_btype_t btyp
 base type of this value
 
ncx_data_class_t dataclass
 config or state data
 
time_t last_modified
 last_modified and etag fields used for filtered retrieval and YANG-API If-Match type of conditional editing
 
ncx_etag_t etag
 ETag for RESTCONF.
 
dlq_hdr_t * metaQ
 YANG does not support user-defined meta-data but NCX does. More...
 
val_editvars_t * editvars
 value editing variables the editvars will only be malloced while edit is in progress More...
 
op_editop_t editop
 needed for all edits
 
status_t res
 validation result
 
dlq_hdr_t * indexQ
 this field used in NCX_BT_LIST only ??? when is it ncx_filptr_t ??? More...
 
ncx_owner_id_t owner_id
 set if the owners are being stored and this is a data node in the running config
 
ncx_nmda_origin_t nmda_origin
 NMDA origin enum.
 

Detailed Description

one value to match one type

Field Documentation

◆ editvars

val_editvars_t* editvars

value editing variables the editvars will only be malloced while edit is in progress

edit-vars from attrs

◆ indexQ

dlq_hdr_t* indexQ

this field used in NCX_BT_LIST only ??? when is it ncx_filptr_t ???

Q of val_index_t or ncx_filptr_t

◆ metaQ

dlq_hdr_t* metaQ

YANG does not support user-defined meta-data but NCX does.

The <edit-config>, <get> and <get-config> operations use attributes in the RPC parameters, the metaQ is still used

The ncx:metadata extension allows optional attributes to be added to object nodes for anyxml, leaf, leaf-list, list, and container nodes. The config property will be inherited from the object that contains the metadata

This is used mostly for RPC input parameters and is strongly discouraged. Full edit-config support is not provided for metadata Q of val_value_t

◆ obj

struct obj_template_t_* obj

common fields

bptr to object def


The documentation for this struct was generated from the following file: