ARES_FREE_HOSTENT(3)

💖 ARES_FREE_HOSTENT 💖

okay bestie, so this one is from the ares library — Library Functions Manual energy, and it's genuinely one of the easiest little pages you'll ever read. the whole job? free the host structure. that's it. that's the gig. she's a one-trick pony and she eats every time. 💅

✨ NAME ✨

ares_free_hostent — free the host structure that the ares functions allocated 🎀

🦋 SYNOPSIS 🦋

#include <ares.h>

void ares_free_hostent(struct hostent *host)

okay so like. that's the whole signature. one pointer, no return value, no drama. struct hostent *host goes in, nothing comes out. iconique. 👑

🌸 DESCRIPTION 🌸

so here's the tea: ares_free_hostent frees a struct hostent that was allocated by one of these three besties:

• ares_parse_a_reply(3)
• ares_parse_aaaa_reply(3)
• ares_parse_ptr_reply(3)

if one of those gave you a host struct, and you're done with it, this is the function that hands it back. no cap. 🫶

💀 NOTES 💀

okay this part is IMPORTANT, so like, actually read it, bestie, i'm begging 🙈

it is not necessary — and lowkey not correct — to free the host structure that gets passed to the callback functions for ares_gethostbyname(3) or ares_gethostbyaddr(3).

⚠️ do NOT free that one. c-ares will automatically free those host structures itself when the callback returns. it's giving "i got this, mind your business." if you free it anyway you're double-freeing and that's a whole mess you do not want. 😭

so to recap the vibe check: parser-allocated host struct → you free it ✅, callback-allocated host struct → hands off, c-ares frees it ❌. iykyk. ✨

🌈 SEE ALSO 🌈

• ares_parse_a_reply(3)
• ares_parse_aaaa_reply(3)
• ares_parse_ptr_reply(3)
• ares_parse_ns_reply(3)

and that's the whole page, bestie!! 🎀✨ this little cutie has been serving since 23 July 1998 (yes she's older than us and still slaying, main character energy fr fr), and it lives in the ARES_FREE_HOSTENT(3) corner of the library functions manual. go free your host structs responsibly. periodt. 💖🦋👑