[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lwip-devel] [task #14314] Implement interface name/index APIs

From: Joel Cunningham
Subject: [lwip-devel] [task #14314] Implement interface name/index APIs
Date: Fri, 3 Feb 2017 21:28:31 +0000 (UTC)
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0

Follow-up Comment #38, task #14314 (project lwip):

The <net/if.h> name is mandated by RFC 3493 under section 7 (Summary of New

I had already added the compatibility header <net/if.h> under the posix folder
which includes lwip/if.h.  I was following the example of netdb.h which uses
the same for the actual header and compatibility header.  The socket header is
very close (lwip/sockets.h vs sys/socket.h)

My preference is for the lwip header stay close to the mandated name since the
if_api.c file is intending to implement the RFC 3493 standard APIs (possibly
other POSIX if APIs in the future).  I have worked with build environments
which also dumped all headers into a global flattened list (terrible I know),
but I'm not sure how common if.h is, maybe if the product had another network

I'll go ahead and make the NETIF_NAMESIZE change and keep in mind the include
architecture for future work :)


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]