rc_dict_addval(3)

πŸ“¦
version 1.5.2 Β· 2 versions
  • 1.5.2 Β· alpine 3.24, epel 10, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0 (latest)
  • 2.0.1 Β· arch rolling
, in alpine 3.24, epel 10, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0

✨ rc_dict_addval β€” the dictionary glow-up function ✨

okay bestie, gather round, because we're talking about rc_dict_addval from the radcli Radius client library manual, section 3 (that's the library-functions section, iykyk πŸ’…). This is the one you call when you want to slide a new value into a dictionary and you're feeling cute about it.


🌸 SYNOPSIS 🌸

#include <radcli/radcli.h>

DICT_VALUE * rc_dict_addval(
    rc_handle   *rh,
    char const  *attrstr,
    char const  *namestr,
    uint32_t     value
);

like, she takes four things and hands you back a pointer. iconic behaviour honestly 🫢


πŸ’– DESCRIPTION πŸ’–

Add value to dictionary. That's the whole mission, that's the assignment, she ate and left no crumbs.

🚨 no cap, important: she does not check if such value already exists. Not even a little. Not even a vibe check. So if you add the same thing twice, that's on you, bestie β€” she's not your babysitter, she's a function. 😭

πŸŽ€ PARAMETERS πŸŽ€

  • rh β€” a handle to configuration. your whole setup lives in here, she needs it to know which dictionary we're talking about.
  • attrstr β€” attribute name. the attribute, as a string, literally.
  • namestr β€” name. yep. that's the name. the name of the value, fr fr.
  • value β€” attribute value. a uint32_t, so bring a real number, not a vibe.

πŸ‘‘ RETURN VALUE πŸ‘‘

  • the added value on success πŸŽ‰
  • NULL on failure πŸ’€

that's it, that's the deal. check your pointer, always, periodt.


πŸ¦‹ SEE ALSO πŸ¦‹

the whole friend group, and yes we're listing every single one of them because we don't do half-finished here:

radcli.h(3), rc_aaa(3), rc_aaa_ctx(3), rc_aaa_ctx_free(3), rc_aaa_ctx_get_secret(3), rc_aaa_ctx_get_vector(3), rc_aaa_ctx_server(3), rc_acct(3), rc_acct_proxy(3), rc_add_config(3), rc_apply_config(3), rc_auth(3), rc_auth_proxy(3), rc_avpair_add(3), rc_avpair_assign(3), rc_avpair_copy(3), rc_avpair_free(3), rc_avpair_gen(3), rc_avpair_get(3), rc_avpair_get_attr(3), rc_avpair_get_in6(3), rc_avpair_get_raw(3), rc_avpair_get_uint32(3), rc_avpair_insert(3), rc_avpair_log(3), rc_avpair_new(3), rc_avpair_next(3), rc_avpair_parse(3), rc_avpair_remove(3), rc_avpair_tostr(3), rc_buildreq(3), rc_check(3), rc_check_tls(3), rc_conf_int(3), rc_conf_srv(3), rc_conf_str(3), rc_config_free(3), rc_config_init(3), rc_destroy(3), rc_dict_addattr(3), rc_dict_addval(3), rc_dict_addvend(3), rc_dict_findattr(3), rc_dict_findval(3), rc_dict_findvend(3), rc_dict_free(3), rc_dict_getattr(3), rc_dict_getval(3), rc_dict_getvend(3), rc_find_server_addr(3), rc_get_socket_type(3), rc_get_srcaddr(3), rc_getport(3), rc_mksid(3), rc_new(3), rc_openlog(3), rc_own_hostname(3), rc_read_config(3), rc_read_dictionary(3), rc_read_dictionary_from_buffer(3), rc_send_server(3), rc_setdebug(3), rc_test_config(3), rc_tls_fd(3)

(and yes, rc_dict_addval(3) links to herself. she's self-referential, she's main character energy, we support her 🌈)


okay that's the whole page, no notes. this one came from radcli and it's dated 2023-01-29 β€” so yeah, she's been serving this exact energy since then and she's not changing for anybody. stay hydrated, check your return values, and don't add duplicates unless you want chaos πŸ’œβœ¨

πŸ“¦ where this page comes from