lightning

History

Rusty Russell 55d962046b Rename (almost) all destructors to destroy_<type>. We usually did this, but sometimes they were named after what they did, rather than what they cleaned up. There are still a few exceptions: 1. I didn't bother creating destroy_xxx wrappers for htable routines which already existed. 2. Sometimes destructors really are used for side-effects (eg. to simply mark that something was freed): these are clearer with boutique names. 3. Generally destructors are static, but they don't need to be: in some cases we attach a destructor then remove it later, or only attach to some cases. These are best with qualifiers in the destroy_<type> name. Suggested-by: @ZmnSCPxj Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>		7 years ago
..
test	wallet: don't implicitly remove peers, but do it explicitly.	7 years ago
.gitignore	wallet: Create and manage a sqlite3 database for the wallet	8 years ago
Makefile	invoices: Extensive reorganization of invoice system.	7 years ago
db.c	Rename (almost) all destructors to destroy_<type>.	7 years ago
db.h	pay: Save nodes and channels used on route to payment.	7 years ago
invoices.c	Rename (almost) all destructors to destroy_<type>.	7 years ago
invoices.h	invoices: Add expiration timer system.	7 years ago
wallet.c	Rename (almost) all destructors to destroy_<type>.	7 years ago
wallet.h	wallet: don't implicitly remove peers, but do it explicitly.	7 years ago
walletrpc.c	lightningd: split struct peer into struct peer and struct channel.	7 years ago
walletrpc.h	walletrpc: Implemented the withdrawal flow	8 years ago