mirror of
https://github.com/aljazceru/lightning.git
synced 2026-02-08 15:44:19 +01:00
fed5a117e7
structeq() is too dangerous: if a structure has padding, it can fail silently. The new ccan/structeq instead provides a macro to define foo_eq(), which does the right thing in case of padding (which none of our structures currently have anyway). Upgrade ccan, and use it everywhere. Except run-peer-wire.c, which is only testing code and can use raw memcmp(): valgrind will tell us if padding exists. Interestingly, we still declared short_channel_id_eq, even though we didn't define it any more! Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
25 lines
307 B
C
25 lines
307 B
C
#include <ccan/structeq/structeq.h>
|
|
|
|
struct mydata1 {
|
|
int start, end;
|
|
};
|
|
|
|
struct mydata2 {
|
|
int start, end;
|
|
};
|
|
|
|
STRUCTEQ_DEF(mydata1, 0, start, end);
|
|
|
|
int main(void)
|
|
{
|
|
struct mydata1 a = { 0, 100 };
|
|
#ifdef FAIL
|
|
struct mydata2
|
|
#else
|
|
struct mydata1
|
|
#endif
|
|
b = { 0, 100 };
|
|
|
|
return mydata1_eq(&a, &b);
|
|
}
|