core-lightning/tools/test/enum.h

#ifndef LIGHTNING_TOOLS_TEST_ENUM_H
#define LIGHTNING_TOOLS_TEST_ENUM_H
#include "config.h"
#include <ccan/short_types/short_types.h>
#include <stdbool.h>
#include <stdlib.h>

#define TEST_IFDEF 0

enum test_enum {
	TEST_ONE,
	TEST_TWO,
};

void towire_test_enum(u8 **pptr, const enum test_enum test_enum);
enum test_enum fromwire_test_enum(const u8 **cursor, size_t *max);
bool printwire_test_enum(const char *fieldname, const u8 **cursor, size_t *max);

#endif /* LIGHTNING_TOOLS_TEST_ENUM_H */
bolt-gen: handle enums Add parsing know-how for enum fields. This is necessary for internally defined wire generators. Enums are denoted by prefixing the field with an `e:`. Ex: msgdata,msg_name,field_name,e:enum_type, 2019-07-23 22:53:44 +02:00			`#ifndef LIGHTNING_TOOLS_TEST_ENUM_H`
			`#define LIGHTNING_TOOLS_TEST_ENUM_H`
check: make sure all files outside contrib/ include "config.h" first. And turn "" includes into full-path (which makes it easier to put config.h first, and finds some cases check-includes.sh missed previously). config.h sets _GNU_SOURCE which really needs to be done before any '#includes': we mainly got away with it with glibc, but other platforms like Alpine may have stricter requirements. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2021-12-04 12:23:56 +01:00			`#include "config.h"`
bolt-gen: handle enums Add parsing know-how for enum fields. This is necessary for internally defined wire generators. Enums are denoted by prefixing the field with an `e:`. Ex: msgdata,msg_name,field_name,e:enum_type, 2019-07-23 22:53:44 +02:00			`#include <ccan/short_types/short_types.h>`
tools/generate-wire.py: have printwire routines do demarshal. This works better in general: let printwire_x do the work of figuring out how to demarshal x. This is particularly important for TLVs, which require a call to tlv_x_new() first. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2022-03-23 00:31:14 +01:00			`#include <stdbool.h>`
bolt-gen: handle enums Add parsing know-how for enum fields. This is necessary for internally defined wire generators. Enums are denoted by prefixing the field with an `e:`. Ex: msgdata,msg_name,field_name,e:enum_type, 2019-07-23 22:53:44 +02:00			`#include <stdlib.h>`

tools: add ability to wrap wire messages with ifs Makes it possible to hide wire messages behind EXPERIMENTAL_FEATURES flag. 2019-09-20 19:49:45 +02:00			`#define TEST_IFDEF 0`

bolt-gen: handle enums Add parsing know-how for enum fields. This is necessary for internally defined wire generators. Enums are denoted by prefixing the field with an `e:`. Ex: msgdata,msg_name,field_name,e:enum_type, 2019-07-23 22:53:44 +02:00			`enum test_enum {`
			`TEST_ONE,`
			`TEST_TWO,`
			`};`

			`void towire_test_enum(u8 **pptr, const enum test_enum test_enum);`
			`enum test_enum fromwire_test_enum(const u8 *cursor, size_t max);`
tools/generate-wire.py: have printwire routines do demarshal. This works better in general: let printwire_x do the work of figuring out how to demarshal x. This is particularly important for TLVs, which require a call to tlv_x_new() first. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2022-03-23 00:31:14 +01:00			`bool printwire_test_enum(const char fieldname, const u8 cursor, size_t max);`
bolt-gen: handle enums Add parsing know-how for enum fields. This is necessary for internally defined wire generators. Enums are denoted by prefixing the field with an `e:`. Ex: msgdata,msg_name,field_name,e:enum_type, 2019-07-23 22:53:44 +02:00
			`#endif /* LIGHTNING_TOOLS_TEST_ENUM_H */`