BSD 4_4 development

[unix-history] / usr / share / man / cat3 / ns_ntoa.0

NS(3)                       BSD Programmer's Manual                      NS(3)

N\bNA\bAM\bME\bE
    n\bns\bs_\b_a\bad\bdd\bdr\br, n\bns\bs_\b_n\bnt\bto\boa\ba - Xerox NS(tm) address conversion routines

S\bSY\bYN\bNO\bOP\bPS\bSI\bIS\bS
    #\b#i\bin\bnc\bcl\blu\bud\bde\be <\b<s\bsy\bys\bs/\b/t\bty\byp\bpe\bes\bs.\b.h\bh>\b>
    #\b#i\bin\bnc\bcl\blu\bud\bde\be <\b<n\bne\bet\btn\bns\bs/\b/n\bns\bs.\b.h\bh>\b>

    _\bs_\bt_\br_\bu_\bc_\bt _\bn_\bs_\b__\ba_\bd_\bd_\br
    n\bns\bs_\b_a\bad\bdd\bdr\br(_\bc_\bh_\ba_\br _\b*_\bc_\bp);

    _\bc_\bh_\ba_\br _\b*
    n\bns\bs_\b_n\bnt\bto\boa\ba(_\bs_\bt_\br_\bu_\bc_\bt _\bn_\bs_\b__\ba_\bd_\bd_\br _\bn_\bs);

D\bDE\bES\bSC\bCR\bRI\bIP\bPT\bTI\bIO\bON\bN
    The routine n\bns\bs_\b_a\bad\bdd\bdr\br() interprets character strings representing XNS ad-
    dresses, returning binary information suitable for use in system calls.
    The routine n\bns\bs_\b_n\bnt\bto\boa\ba() takes XNS addresses and returns ASCII strings rep-
    resenting the address in a notation in common use in the Xerox Develop-
    ment Environment:

          <network number>.<host number>.<port number>

    Trailing zero fields are suppressed, and each number is printed in hex-
    adecimal, in a format suitable for input to n\bns\bs_\b_a\bad\bdd\bdr\br().  Any fields lack-
    ing super-decimal digits will have a trailing `H' appended.

    Unfortunately, no universal standard exists for representing XNS address-
    es.  An effort has been made to insure that n\bns\bs_\b_a\bad\bdd\bdr\br() be compatible with
    most formats in common use.  It will first separate an address into 1 to
    3 fields using a single delimiter chosen from period `.', colon `:' or
    pound-sign `#'. Each field is then examined for byte separators (colon or
    period).  If there are byte separators, each subfield separated is taken
    to be a small hexadecimal number, and the entirety is taken as a network-
    byte-ordered quantity to be zero extended in the high-network-order
    bytes.  Next, the field is inspected for hyphens, in which case the field
    is assumed to be a number in decimal notation with hyphens separating the
    millenia.  Next, the field is assumed to be a number: It is interpreted
    as hexadecimal if there is a leading `0x' (as in C), a trailing `H' (as
    in Mesa), or there are any super-decimal digits present.  It is inter-
    preted as octal is there is a leading `0' and there are no super-octal
    digits.  Otherwise, it is converted as a decimal number.

R\bRE\bET\bTU\bUR\bRN\bN V\bVA\bAL\bLU\bUE\bES\bS
    None. (See _\bB_\bU_\bG_\bS.)

S\bSE\bEE\bE A\bAL\bLS\bSO\bO
    hosts(5),  networks(5),

H\bHI\bIS\bST\bTO\bOR\bRY\bY
    The n\bns\bs_\b_a\bad\bdd\bdr\br() and n\bns\bs_\b_t\bto\boa\ba() functions appeared in 4.3BSD.

B\bBU\bUG\bGS\bS
    The string returned by n\bns\bs_\b_n\bnt\bto\boa\ba() resides in a static memory area.  The
    function n\bns\bs_\b_a\bad\bdd\bdr\br() should diagnose improperly formed input, and there
    should be an unambiguous way to recognize this.

4.3 Berkeley Distribution        June 4, 1993                                1