[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [lwip-devel] IPv6 design considerations
From: |
Bill Auerbach |
Subject: |
RE: [lwip-devel] IPv6 design considerations |
Date: |
Mon, 8 Nov 2010 17:21:22 -0500 |
Ivan,
>This requires some refactoring, as all code must be changed as follows:
> pcb->local_ip to: pcb->local_ip.ip4
>
>I hope it is acceptable to make this change throughout?
You can probably use a conditional macro:
#if IPV4
#define local_ip local_ip.ip4
#else // both IPv4 and IPv6
#define local_ip local_ip
#endif
Of course, this must be included *after* the local_ip union declaration.
So for IPV4 the source looks the same and for IPv4/IPv6 the union is used.
In any case, I'm trying to help find a way to not edit all of the references
- it should be possible. The preprocessor is quite powerful.
Bill
- [lwip-devel] IPv6 design considerations, Ivan Delamer, 2010/11/08
- Re: [lwip-devel] IPv6 design considerations, Kieran Mansley, 2010/11/08
- RE: [lwip-devel] IPv6 design considerations,
Bill Auerbach <=
- Re: [lwip-devel] IPv6 design considerations, Simon Goldschmidt, 2010/11/09
- RE: [lwip-devel] IPv6 design considerations, Bill Auerbach, 2010/11/09
- Re: [lwip-devel] IPv6 design considerations, Kieran Mansley, 2010/11/09
- Re: [lwip-devel] IPv6 design considerations, Ivan Delamer, 2010/11/09