Re: [lwip-devel] Behaviour of netifapi_netif_set_addr()

[Dirk Ziegelmeier]

yes, I think it should be in netif_set_addr. But I'm unsure if this is a compatibility issue for some users. Maybe Simon has an opinion about it?

Ciao
Dirk

--
Dirk Ziegelmeier * address@hidden * http://www.ziegelmeier.net

On Tue, Apr 5, 2016 at 3:55 PM, Freddie Chopin <address@hidden> wrote:

On wto, 2016-04-05 at 13:27 +0200, Dirk Ziegelmeier wrote:
> sorry, special treatment of NULL to avoid too many functions

Would it make sense to implement such special treatment directly
in netif_set_addr()? This way the whole thing would be consistent -
netifapi_netif_set_addr() would still be a wrapper for
netif_set_addr(), nothing special about it. Personally I would prefer
this option.

If such special treatment would be implemented only
in netifapi_netif_set_addr(), then this function would no longer be
equivalent to netif_set_addr()...

If one really wants to set any of the addresses to 0, then there's no
problem - instead of NULL, just use IPADDR_ANY.

Regards,
FCh

_______________________________________________
lwip-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/lwip-devel