shishi_krberror_errorcode(3)

πŸ“¦
version 1.0.3 Β· 2 versions
  • 1.0.3 Β· debian bookworm, debian trixie, nixos 26.05, nixpkgs unstable, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking (latest)
  • 1.0.2 Β· ubuntu jammy
, in debian bookworm, debian trixie, nixos 26.05, nixpkgs unstable, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ’– shishi_krberror_errorcode(3) πŸ’–

okay bestie, sit down, hydrate, and let me tell you about this little icon from the shishi manual. it's a section 3 page, so it's a library function, and it is so useful. no cap.


✨ NAME ✨

shishi_krberror_errorcode β€” API function πŸŽ€

like, that's it. that's the name. short, sweet, main character energy.


✨ SYNOPSIS ✨

okay so here's how you pull her into your code:

#include <shishi.h>

int shishi_krberror_errorcode(Shishi * handle, Shishi_asn1 krberror,
       int32_t * errorcode);

yes, three arguments. yes, one of them is a pointer-to-pointer situation (okay not really, but the output param vibe is real). we'll get there. πŸ¦‹


✨ ARGUMENTS ✨

  • Shishi * handle β€” the shishi handle, babes. and like, specifically one that was allocated by shishi_init(). don't be out here passing some random uninitialised handle, i am begging πŸ™ˆ
  • Shishi_asn1 krberror β€” a KRB-ERROR structure that has an error code in it. that's the whole point. it's the thing you're reading from.
  • int32_t * errorcode β€” output integer. like, you pass in a pointer and it gets filled with the KRB-ERROR error code. classic out-param behaviour, she's giving very much "i'll write into your pointer" πŸ’…

✨ DESCRIPTION ✨

so what does she actually DO? she extracts the error code from KRB-ERROR. that's it. that's the function. lowkey simple, highkey essential. if you've got a KRB-ERROR structure just sitting there being mysterious, this is the girl who goes in and pulls the error code out for you. 🫢


✨ RETURN VALUE ✨

returns SHISHI_OK iff successful. and bestie, notice that "iff" β€” that's if and only if, so if you get anything other than SHISHI_OK back, something went sideways and you should probably, like, deal with it. not me ignoring return values. couldn't be me. 😭


✨ REPORTING BUGS ✨

found a bug? first of all, iconic of you for caring. second of all, report it to:

bug-shishi@gnu.org

GNU Shishi home page: http://www.gnu.org/software/shishi/

general help using GNU software: http://www.gnu.org/gethelp/

go forth and file that report, queen πŸ‘‘


Copyright Β© 2002-2022 Simon Josefsson.

and the license is the chillest one fr fr: copying and distribution of this file, with or without modification, are permitted in any medium without royalty provided the copyright notice and this notice are preserved. so like, share it, remix it, whatever β€” just keep the receipts. 🧚


✨ SEE ALSO ✨

the full documentation for shishi is maintained as a Texinfo manual. so if the info and shishi programs are properly installed at your site, this command:

info shishi

should give you access to the complete manual. go read the whole thing, it's giving lore. 🌈


and that's the page, bestie!! you now know everything this function has to offer, no skips, no summarising, every single detail intact because that's just how we do it here. πŸ’œ

🌸 this has been shishi_krberror_errorcode(3), from the shishi manual, version 1.0.3 β€” stay slaying, stay compiling, and remember: SHISHI_OK or it didn't happen. periodt. πŸ’…βœ¨