From 01cbfcba4bc74fb04904ad395a346549853bd189 Mon Sep 17 00:00:00 2001 From: Nick Alcock Date: Thu, 18 Mar 2021 12:37:52 +0000 Subject: libctf: fix comment above ctf_dict_t It is perfectly possible to have dynamically allocated data owned by a specific dict: you just have to teach ctf_serialize about it. libctf/ChangeLog 2021-03-18 Nick Alcock * ctf-impl.h (ctf_dict_t): Fix comment. --- libctf/ctf-impl.h | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) (limited to 'libctf/ctf-impl.h') diff --git a/libctf/ctf-impl.h b/libctf/ctf-impl.h index 78a41ff..5567b4c 100644 --- a/libctf/ctf-impl.h +++ b/libctf/ctf-impl.h @@ -372,11 +372,12 @@ typedef struct ctf_dedup ctf_dict_t typedef appears in and declares a forward tag. (A ctf_file_t typedef also appears there, for historical reasons.) - NOTE: ctf_serialize() requires that everything inside of ctf_dict either be - an immediate value, a pointer to dynamically allocated data *outside* of the - ctf_dict itself, or a pointer to statically allocated data. If you add a - pointer to ctf_dict that points to something within the ctf_dict itself, you - must make corresponding changes to ctf_serialize(). */ + NOTE: ctf_serialize requires that everything inside of ctf_dict either be an + immediate value, a pointer to dynamically allocated data *outside* of the + ctf_dict itself, a pointer to statically allocated data, or specially handled + in ctf_serialize. If you add a pointer to ctf_dict that points to something + within the ctf_dict itself, you must make corresponding changes to + ctf_serialize. */ struct ctf_dict { -- cgit v1.1