solaris Man Page: fn_ctx_get_syntax

Man Pages

Back to Software Index BORDER=0

Manpage Top Level

fn_ctx_get_syntax_attrs(3N) manual page Table of Contents

Name

fn_ctx_get_syntax_attrs - return syntax attributes associated with named context

Synopsis

cc [ flag ... ] file ... -lxfn [ library ... ]

#include <xfn/xfn.h>

FN_attrset_t *fn_ctx_get_syntax_attrs(FN_ctx_t *ctx, const FN_composite_name_t *name, FN_status_t *status);

Description

Each context has an associated set of syntax-related attributes. This operation returns the syntax attributes associated with the context named by name relative to the context ctx.

The attributes must contain the attribute fn_syntax_type ( FN_ID_STRING format). If the context supports a syntax that conforms to the XFN standard syntax model, fn_syntax_type is set to "standard" (ASCII attribute syntax) and the attribute set contains the rest of the relevant syntax attributes described in xfn_compound_names(3N) .

This operation is different from other XFN attribute operations in that these syntax attributes could be obtained directly from the context. Attributes obtained through other XFN attribute operations may not necessarily be associated with the context; they may be associated with the reference of context, rather than the context itself (see xfn_attributes(3N) ).

Return Value

fn_ctx_get_syntax_attrs() returns an attribute set if successful; it returns a NULL pointer (0) if the operation fails.

Errors

fn_ctx_get_syntax_attrs() sets status as described in FN_status_t(3N) and xfn_status_codes(3N) .

Application Usage

Implementations may choose to support other syntax types in addition to, or in place of, the XFN standard syntax model, in which case, the value of the fn_syntax_type attribute would be set to an implementation-specific string, and different or additional syntax attributes will be in the set.

Syntax attributes of a context may be generated automatically by a context, in response to fn_ctx_get_syntax_attrs(), or they may be created and updated using the base attribute operations. This is implementation-dependent.