TLSRPT_ER...RROR_CODE(3)

πŸ’– NAME πŸ’–

tlsrpt_errno_from_error_code β€” bestie, this one hands you back the errno part of an errorcode ✨


πŸŽ€ SYNOPSIS πŸŽ€

#include <tlsrpt.h>

int tlsrpt_errno_from_error_code(int errorcode)

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so here's the vibe πŸ‘‘ β€” tlsrpt_errno_from_error_code takes an errorcode and gives you back just the errno part of it. that's it, that's the whole job, and she does it flawlessly πŸ’…

but wait, there's a lil plot twist 🫢 when the error comes from internal library errors living in the TLSRPT_ERR_TLSRPT block, the number she returns is highkey big on purpose β€” a high number β€” so it doesn't clash with the errno values that already exist out there in the wild. no collisions, no drama, no tears 😭

the receipts, fr fr: TLSRPT_ERR_TLSRPT_NESTEDPOLICY is literally 10731 instead of 10031, and the reason is iconic β€” that way the errno part doesn't get misread as EMLINK. like, imagine getting decoded as the wrong error. embarrassing. we don't do that here 🌸


✨ RETURN VALUE ✨

  • On success β€” you get 0. slay. πŸŽ€
  • On failure β€” you get a combined error code, which you can then dig into with the tlsrpt_strerror function πŸ”

🌈 SEE ALSO 🌈

  • man:tlsrpt_error_code_is_internal[3]
  • man:tlsrpt_strerror[3]

πŸ’œ AUTHOR πŸ’œ

Boris Lohner 🫢 (yes legend, we see you)


so yeah, that's tlsrpt_errno_from_error_code from the TLSRPT_ER...RROR_CODE(3) page, dated 2026-05-12 🌸 go forth and decode your errnos, bestie, you got this πŸ’–βœ¨πŸ’…

πŸ“¦ where this page comes from