TLSRPT_FINISH_POLICY(3)

πŸ’– TLSRPT_FINISH_POLICY πŸ’–

okay bestie, you found the tlsrpt_finish_policy page in section 3 of the manual β€” she's a libtlsrpt girlie and she's here to close out your policy for you πŸŽ€


✨ NAME ✨

tlsrpt_finish_policy β€” finishes a policy within a delivery request πŸ’…


🌸 SYNOPSIS 🌸

#include <tlsrpt.h>

int tlsrpt_finish_policy(struct tlsrpt_dr_t* dr, tlsrpt_final_result_t
final_result)

πŸ¦‹ DESCRIPTION πŸ¦‹

so. tlsrpt_finish_policy finishes a policy inside a delivery request. That's it, that's the job. She wraps things up and frees all the resources that tlsrpt_init_policy allocated β€” like, every single one, she's thorough like that πŸ’–

and this is the part where I need you to lock in, bestie: every single call to tlsrpt_init_policy MUST be matched by a call to tlsrpt_finish_policy. Not "should", not "ideally" β€” must. It's giving matched set, it's giving soulmates, it's giving you don't get to open it and ghost it πŸ˜­πŸ’€

⚠️ Note: the library does NOT do any plausibility checks about how many failures you added to this policy versus what final result you're reporting. So like… it's totally possible to finish a policy as TLSRPT_FINAL_FAILURE with no failures added at all, and it's just as possible to finish a policy as TLSRPT_FINAL_SUCCESS with one or more failures added. The library is not your mom, she is not checking your work πŸ™ˆ

πŸ’œ RETURN VALUE πŸ’œ

tlsrpt_finish_policy returns 0 on success πŸŽ‰ and a combined error code on failure 😭. That combined error code can be analyzed with the tlsrpt_strerror function β€” so if something goes sideways, that's your girl for decoding the drama πŸ”βœ¨


πŸ‘‘ SEE ALSO πŸ‘‘

  • tlsrpt_init_policy[3]
  • tlsrpt_strerror[3]
  • tlsrpt_error_code_is_internal[3]

iykyk, go read those next, they're iconic in their own right 🫢


πŸ’« AUTHOR πŸ’«

Boris Lohner ✨ (yes, we're crediting the icon, always)


and that's the whole page, bestie!! this was tlsrpt_finish_policy from the tlsrpt_finish_policy manual, dated 2026-05-12, living in section TLSRPT_FINISH_POLICY(3). now go call your tlsrpt_finish_policy and free your resources, you main character πŸ§šπŸ’–πŸŒΈ

πŸ“¦ where this page comes from