getdns_dict_get(3)

💖 getdns_dict_get — the manual page, but make it fashion 💖

okay bestie, so this is from the getdns family, and it's the one where you go digging into a dict. like, you have a name, and you want the value behind it. that's it, that's the whole gig. ✨

---

🌸 NAME 🌸

getdns_dict_get, getdns_dict_get_bindata, getdns_dict_get_data_type, getdns_dict_get_dict, getdns_dict_get_int, getdns_dict_get_list, getdns_dict_get_names — basically: grab a value by name out of a getdns dict. the whole little squad of getters, all in one place. 🫶

---

📚 LIBRARY 📚

DNS Resolver library (libgetdns, -lgetdns) 💅

---

✨ SYNOPSIS ✨

okay so here's the lineup, copy-paste ready, exactly as it is:

#include <getdns.h>

getdns_return_t
getdns_dict_get_bindata (getdns_dict *this_dict,
   char *name,
   getdns_bindata **answer)

getdns_return_t
getdns_dict_get_data_type (getdns_dict *this_dict,
   char *name,
   getdns_data_type *answer)

getdns_return_t
getdns_dict_get_dict (getdns_dict *this_dict,
   char *name,
   getdns_dict **answer)

getdns_return_t
getdns_dict_get_int (getdns_dict *this_dict,
   char *name,
   uint32_t *answer)

getdns_return_t
getdns_dict_get_list (getdns_dict *this_dict,
   char *name,
   getdns_list **answer)

getdns_return_t
getdns_dict_get_names (getdns_dict *this_dict,
   getdns_list **answer)

notice there's one getter per type bestie — you gotta tell it which flavor you're expecting. no vibes-based type guessing here, it's giving strict. 😭

---

👑 DESCRIPTION 👑

the getdns_dict type is the one that runs the whole name/value pairs situation. the names are strings, and the values? they're heterogeneous — meaning they do NOT all match, and honestly? slay. the value types you might find in there are:

• getdns_bindata
• getdns_dict
• getdns_list
• uint32_t

and now the arguments, one by one, no skipping:

• this_dict — the dictionary from which to retrieve the list of names. it's the home base, the one you're searching through. 🏠
• name — the name whose associated value is to be returned in answer. you want the thing behind this key. 🔑
• answer — the list of all names in the dictionary. and bestie, listen to me on this one: note that the caller must free storage allocated to the list via a call to getdns_list_destroy(3). that memory is yours to clean up. not doing it is giving leak energy. 🚮

---

🌈 RETURN VALUES 🌈

when everything goes right, these functions hand you back GETDNS_RETURN_GOOD. periodt. 💚

but if it does NOT go right, here's what you might catch instead:

• GETDNS_RETURN_GOOD — successful completion, the good ending, the main character moment. ⭐
• GETDNS_RETURN_GENERIC_ERROR — thrown when this_dict is not a valid dictionary. like, that's not even a dict bestie, what am I supposed to do with that. 💀
• GETDNS_RETURN_NO_SUCH_DICT_NAME — when the name argument doesn't exist in the dictionary. you asked for a key that simply is not there. tragic. 😭
• GETDNS_RETURN_WRONG_TYPE_REQUESTED — when the requested data type doesn't match the contents of the indexed argument or name. you said int, it's actually a list, the vibe check failed. 🙈

ngl, GETDNS_RETURN_WRONG_TYPE_REQUESTED is the one that's gonna humble you the most. always know your types before you reach in. 💅

---

🧚 EXAMPLES 🧚

TBD

yep. that's it. that's the example section. iconic of them honestly. ✨

---

🔥 SEE ALSO 🔥

go read these next, bestie, they're all part of the lore:

• libgetdns(3)
• getdns_address(3)
• getdns_dict(3)
• getdns_dict_set(3)
• getdns_general(3)
• getdns_hostname(3)
• getdns_list(3)
• getdns_service(3)

---

and that's the whole page, no cap. this was getdns 1.7.3, dated December 2015 — shoutout to the source and the version for making all this possible. go forth and get your dict values responsibly, bestie. 🎀💖🦋