[Top][All Lists]

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

[lwip-devel] API change: restructuring ipv4/ipv6 integration (task #1272

From: address@hidden
Subject: [lwip-devel] API change: restructuring ipv4/ipv6 integration (task #12722)
Date: Thu, 09 Apr 2015 22:19:53 +0200
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0

Hi all,

for those not reading lwip-users:

goldsimon wrote:
I just wanted to warn you I'm going to push a rather big change
regarding ipv4/ipv6 integration where the old 'ip_addr_t' will be
renamed to ip4_addr_t and ip_addr_t changed to replace ipX_addr_t,
including a version information. This ensures ipv4 and ipv6 addresses
are handled equal (more or less).

This results in an API change, which should hopefully not be noticed by
ipv4-only users (LWIP_IPV6==0). In case it does change anything, please
reply here!

This is in preparation for the 1.5.0 release, but I expect more changes
in this area after possibly discussing this further on lwip-devel, so
the API might change again in the next weeks or so. So unless you really
want to follow development, I suggest to not pull master tip unless we
have sorted this out.

This mainly means that the tcp/udp/raw API uses dual-version IP addresses everywhere and most of the IPv6-specific functions/defines are removed.

I'm just pushing this now to get forward on 1.5.0, but please feel free to share your critics here!

I hope that there are no compiler errors left, but given the amount of possible define-combinations and function-like-defines I might not all use, chances are I missed some, so please share them here if you find any.

The next step (which I already started with that commit) is task #13480 (lwIP as IPv6 only stack).


reply via email to

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