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

NAME
     fn_ctx_lookup_link - look up the link reference bound  to  a
     name

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

     FN_ref_t    *fn_ctx_lookup_link(FN_ctx_t     *ctx,     const
     FN_composite_name_t *name, FN_status_t *status);

DESCRIPTION
     This operation returns the XFN link bound to name.  The ter-
     minal atomic part of name must be bound to an XFN link.

     The normal  fn_ctx_lookup(3XFN) operation follows all  links
     encountered, including any bound to the terminal atomic part
     of name. This operation differs from the  normal  lookup  in
     that  when  the terminal atomic part of name is an XFN link,
     this link is not followed, and  the  operation  returns  the
     link.

RETURN VALUES
     If   fn_ctx_lookup_link()  fails,  a  NULL  pointer  (0)  is
     returned.

ERRORS
     fn_ctx_lookup_link()   sets    status   as   described    in
     FN_status_t(3XFN)  and  xfn_status_codes(3XFN).  Of  special
     relevance for fn_ctx_lookup_link() is the  following  status
     code:

     FN_E_MALFORMED_LINK
           name resolved to a reference that was not a link.

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_ctx_lookup(3XFN),      xfn(3XFN),
     xfn_links(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.

Партнёры:

Хостинг: