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  <nick.alcock@oracle.com>

	* ctf-impl.h (ctf_dict_t): Fix comment.
This commit is contained in:
Nick Alcock
2021-03-18 12:37:52 +00:00
parent bf4c3185a5
commit 01cbfcba4b
2 changed files with 10 additions and 5 deletions

View File

@ -1,3 +1,7 @@
2021-03-18 Nick Alcock <nick.alcock@oracle.com>
* ctf-impl.h (ctf_dict_t): Fix comment.
2021-03-18 Nick Alcock <nick.alcock@oracle.com>
* ctf-create.c (symtypetab_delete_nonstatic_vars): Move

View File

@ -372,11 +372,12 @@ typedef struct ctf_dedup
ctf_dict_t typedef appears in <ctf-api.h> 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
{