> After some digging, it seems /usr/include/sys/socket.h is relevant:
>
> /*
> * Address families.
> */
> #define AF_UNSPEC 0 /* unspecified */
> #define AF_UNIX 1 /* local to host (pipes, portals) */
> #define AF_INET 2 /* internetwork: UDP, TCP, etc. */
> #define AF_IMPLINK 3 /* arpanet imp addresses */
> #define AF_PUP 4 /* pup protocols: e.g. BSP */
> #define AF_CHAOS 5 /* mit CHAOS protocols */
> #define AF_NS 6 /* XEROX NS protocols */
> #define AF_ISO 7 /* ISO protocols */
> #define AF_OSI AF_ISO
> #define AF_ECMA 8 /* european computer manufacturers */
> #define AF_DATAKIT 9 /* datakit protocols */
> #define AF_CCITT 10 /* CCITT protocols, X.25 etc */
> #define AF_SNA 11 /* IBM SNA */
> #define AF_DECnet 12 /* DECnet */
> #define AF_DLI 13 /* Direct data link interface */
> #define AF_LAT 14 /* LAT */
> #define AF_HYLINK 15 /* NSC Hyperchannel */
> #define AF_APPLETALK 16 /* Apple Talk */
> #define AF_ROUTE 17 /* Internal Routing Protocol */
> #define AF_LINK 18 /* Link layer interface */
> #define pseudo_AF_XTP 19 /* eXpress Transfer Protocol (no AF)
> */
>
> #define AF_MAX 20
>
> /*
> * Structure used by kernel to store most addresses.
> */
> struct sockaddr {
> u_short sa_family; /* address family */
> char sa_data[14]; /* up to 14 bytes of direct
> address */
> };
>
> Any suggestions on a curl convention to follow with respect to
> handling this variance to what other systems define?
After more digging, I see CURL_SA_FAMILY_T...
Kevin R. Bulgrien
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.se/mail/etiquette.html
