[ новости /+++ | форум | теги | ]

NAME
     fn_ctx_list_bindings, FN_bindinglist_t, fn_bindinglist_next,
     fn_bindinglist_destroy  -  list  the atomic names and refer-
     ences bound in a context

SYNOPSIS
     cc [ flag ... ] file ... -lxfn [ library ... ]
     #include <xfn/xfn.h>

     FN_bindinglist_t *fn_ctx_list_bindings(FN_ctx_t *ctx,  const
     FN_composite_name_t *name, FN_status_t *status);

     FN_string_t    *fn_bindinglist_next(FN_bindinglist_t    *bl,
     FN_ref_t **ref, FN_status_t *status);

     void      fn_bindinglist_destroy(FN_bindinglist_t       *bl,
     FN_status_t *status);

DESCRIPTION
     This set of operations is used to list the names  and  bind-
     ings  in  the context named by  name relative to the context
     ctx. Note that  name must name a context. If the  intent  is
     to  list the contents of ctx, name should be an empty compo-
     site name.

     The semantics of these operations are similar to  those  for
     listing names (see  fn_ctx_list_names(3XFN)). In addition to
     a name string being  returned,   fn_bindinglist_next()  also
     returns  the reference of the binding for each member of the
     enumeration.

ATTRIBUTES
     See attributes (5) for descriptions of the following  attri-
     butes:

     ____________________________________________________________
    |       ATTRIBUTE TYPE        |       ATTRIBUTE VALUE       |
    |_____________________________|_____________________________|
    | MT-Level                    | MT-Safe                     |
    |_____________________________|_____________________________|


SEE ALSO
     FN_composite_name_t(3XFN),  FN_ctx_t(3XFN),  FN_ref_t(3XFN),
     FN_status_t(3XFN),                        FN_string_t(3XFN),
     fn_ctx_list_names(3XFN), xfn(3XFN),  xfn_status_codes(3XFN),
     attributes(5)

NOTES
     The implementation of XFN in this Solaris release  is  based
     on  the  X/Open preliminary specification. It is likely that
     there will be minor changes to these interfaces  to  reflect
     changes in the final version of this specification. The next
     minor release of Solaris will offer binary compatibility for
     applications  developed using the current interfaces. As the
     interfaces evolve toward  standardization,  it  is  possible
     that  future  releases  of Solaris will require minor source
     code  changes  to  applications  that  have  been  developed
     against the preliminary specification.

Партнёры:

Хостинг: