IXP_PRINT(3)

πŸ“¦ version 0-unstable-2022-04, in nixos 26.05, nixpkgs unstable

okay so this is IXP_PRINT(3), a page from the Library Functions Manual for libixp β€” and yes bestie, we’re getting into formatted IO πŸ’…βœ¨

πŸ’– NAME πŸ’–

ixp_print, ixp_vprint, ixp_vsmprint β€” the libixp formatted-IO girlies πŸŽ€

✨ SYNOPSIS ✨

#include <ixp.h>

int ixp_print(IxpCFid *fid, const char *fmt, ...);

int ixp_vprint(IxpCFid *fid, const char *fmt, va_list args);

char*    (*ixp_vsmprint)(const char *fmt, va_list);

πŸŽ€ PARAMETERS πŸŽ€

  • fid β€” an open IxpCFid to which to write the result. literally the destination, bestie 🫢
  • fmt β€” the string with which to format the data. the format-string main character ✨
  • args β€” a va_list holding the arguments to the format string. the lil squad of values πŸ’œ
  • ... β€” the arguments to the format string. same energy, just inline πŸ™ˆ

πŸ¦‹ DESCRIPTION πŸ¦‹

These functions act like the standard formatted IO functions. They write the result of the formatting to the file pointed to by fid. no cap, that’s the whole vibe πŸ¦‹

ixp_vsmprint(3) may be set to a function which will format its arguments and return a nul-terminated string allocated by malloc(3). The default formats its arguments as printf(3). iconic default behavior, fr fr πŸ’…

🌸 RETURN VALUE 🌸

These functions return the number of bytes written. There is currently no way to detect failure. yes, bestie, that means failure detection is lowkey not a thing here 😭 keep that in mind!

🌈 SEE ALSO 🌈


xoxo, the libixp Manual πŸ’– β€” 2012 Dec edition, page IXP_PRINT(3) πŸŽ€βœ¨

πŸ“¦ where this page comes from