Personally, I think unit tests are a good idea to ensure changes in some
area of the code don't break other areas. And of course the tests can be
put into a different directory (even accessing static variables - e.g.
the ARP table in etharp.c - can be achieved outside of the original code
files).
But _if_ we include tests, we would have to make sure everyone really
uses them (and runs them before making big changes etc.). If they are
not used often, they aren't worth much. In other words, I think the
project leader should ensure they don't get forgotten ;-)
Simon
_______________________________________________
lwip-users mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/lwip-users
