SAFE_INIT_ID_RANGE_LIST(3)

πŸ“¦ version 1.0.5, in nixos 26.05, nixpkgs unstable

πŸ’– NAME πŸ’–

okay so bestie, this is the SAFE_INIT_ID_RANGE_LIST(3) page, and it's literally about safe_init_id_range_list and safe_destroy_id_range_list β€” the duo that create and destroy id range lists. no cap. πŸŽ€

πŸ“š SYNOPSIS πŸ“š

#include "safe_id_range_list.h"

struct safe_id_range_list;
typedef struct safe_id_range_list safe_id_range_list;

int  safe_init_id_range_list(safe_id_range_list list);
void safe_destroy_id_range_list(safe_id_range_list list);

πŸ’… DESCRIPTION πŸ’…

safe_init_id_range_list initializes a safe_id_range_list structure. you must call it before the function can be used β€” that's not optional, bestie. ✨

safe_destroy_id_range_list frees the memory used by a safe_id_range_list data structure, and you should call it after all uses of the safe_id_range_list structure are complete. it's the cleanup era. πŸ§ΉπŸ’–

🌸 Parameters 🌸

  • list β€” the safe_id_range_list to operate on. the value must be non-NULL. do not test her with a NULL, okay? πŸ™ˆ

πŸ”₯ RETURN VALUE πŸ”₯

safe_init_id_range_list return 0 on success and -1 on failure. yes, classic 0/-1 behavior, very demure. πŸ’…

safe_destroy_id_range_list returns nothing. in the case of an error, errno is set appropriately. so even the no-return function has a little drama in the error channel. πŸ’€

😭 ERRORS 😭

  • EINVAL β€” the list parameter was NULL. bestie, you cannot pass NULL; that's the whole thing. 🫢
  • ENOMEM β€” safe_init_id_range_list failed to allocate memory. the allocation did not slay, unfortunately. 😭

πŸ‘‘ AUTHOR πŸ‘‘

James A. Kupsch β€” iconic behavior, honestly. 🌟

πŸ¦‹ SEE ALSO πŸ¦‹


this page is serving 2011-07-26 SAFE_INIT_ID_RANGE_LIST(3) energy, sign-off complete πŸ’…βœ¨

πŸ“¦ where this page comes from