4.3BSD-Reno/share/man/cat3/ns_addr.0

Compare this file to the similar file:
Show the results in this format:




NS(3)			      1990			    NS(3)



NNAAMMEE
     ns_addr, ns_ntoa - Xerox NS(tm)  address conversion routines

SSYYNNOOPPSSIISS
     ##iinncclluuddee <<ssyyss//ttyyppeess..hh>>
     ##iinncclluuddee <<nneettnnss//nnss..hh>>

     ssttrruucctt nnss__aaddddrr nnss__aaddddrr((ccpp))
     cchhaarr **ccpp;;

     cchhaarr **nnss__nnttooaa((nnss))
     ssttrruucctt nnss__aaddddrr nnss;;

DDEESSCCRRIIPPTTIIOONN
     The routine _n_s__a_d_d_r interprets character strings represent-
     ing XNS addresses, returning binary information suitable for
     use in system calls.  _n_s__n_t_o_a takes XNS addresses and
     returns ASCII strings representing the address in a notation
     in common use in the Xerox Development Environment:
	  <network number>.<host number>.<port number>
     Trailing zero fields are suppressed, and each number is
     printed in hexadecimal, in a format suitable for input to
     _n_s__a_d_d_r.  Any fields lacking super-decimal digits will have
     a trailing ``H'' appended.

     Unfortunately, no universal standard exists for representing
     XNS addresses.  An effort has been made to insure that
     _n_s__a_d_d_r 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
     interpreted as octal is there is a leading ``0'' and there
     are no super-octal digits.  Otherwise, it is converted as a
     decimal number.

SSEEEE AALLSSOO
     hosts(5), networks(5),

DDIIAAGGNNOOSSTTIICCSS
     None (see BUGS).





Printed 7/27/90               June				1






NS(3)			      1990			    NS(3)



BBUUGGSS
     The string returned by _n_s__n_t_o_a resides in a static memory
     area.
     _n_s__a_d_d_r should diagnose improperly formed input, and there
     should be an unambiguous way to recognize this.


















































Printed 7/27/90               June				2