gd_alter_affixes(3)

💅 gd_alter_affixes — bestie edition 💅

okay so this is a page from the GETDATA manual, section 3, and it's literally all about gd_alter_affixes(). no cap. let's get into it 🫶

✨ NAME ✨

gd_alter_affixes — modify the field affixes of a fragments in a Dirfile 💖

(that "a fragments" is the original's grammar, not mine, i'm just the messenger 🎀)

🌸 SYNOPSIS 🌸

#include <getdata.h>

int gd_alter_affixes(DIRFILE *dirfile, int fragment_index, const char
       *prefix, const char *suffix);

🦋 DESCRIPTION 🦋

so what does this icon actually DO? the gd_alter_affixes() function sets the root namespace, field prefix and suffix of fields defined in the format specification fragment given by fragment_index to prefix and suffix in the dirfile(5) database specified by dirfile. slay 💅

the prefix may contain a root namespace for the fragment, separated from the prefix by a dot (.). if it does not contain a namespace, the fragment's root namespace is not changed. and if you wanna remove a root namespace? you explicitly specify the null namespace via a leading dot in prefix. periodt.

the field prefix and suffix get affixed to all field codes found in the specified fragment. lowkey important: if the parent fragment to the modified fragment contains field affixes themselves, they should be included in the affixes passed to gd_alter_affixes(). yes bestie, you gotta be thorough. if prefix or suffix is NULL, the corresponding affix will be unchanged. and to remove an affix, set it to the parent fragment's corresponding affix, which may be the empty string ("").

🚫 it is not possible to set affixes on the root format file (i.e. fragment_index may not be zero). just... no.

the dirfile argument must point to a valid DIRFILE object previously created by a call to gd_open(3). don't be out here passing random stuff, i'm begging 🙈

⭐ RETURN VALUE ⭐

upon successful completion, gd_alter_affixes() returns zero. on error, it returns a negative-valued error code. possible error codes are:

• GD_E_ACCMODE — the specified dirfile was opened read-only. bestie you can't edit what you didn't open for editing 😭
• GD_E_ALLOC — the library was unable to allocate memory.
• GD_E_BAD_CODE — the supplied prefix or suffix contained invalid characters. rude of you ngl.
• GD_E_BAD_DIRFILE — the supplied dirfile was invalid.
• GD_E_BAD_INDEX — the supplied index was out of range.
• GD_E_DUPLICATE — the supplied affixes would result in one or more field codes duplicating an existing field code. we do NOT do dupes here 💀
• GD_E_PROTECTED — the metadata of the given fragment's parent fragment was protected from change. hands off, it's guarded 🛡️

the error code is also stored in the DIRFILE object and may be retrieved after this function returns by calling gd_error(3). and a descriptive error string for the error may be obtained by calling gd_error_string(3). so you'll never be left guessing, we love that for us ✨

🎀 NOTES 🎀

the function gd_fragment_namespace(3) can also be used to modify the root namespace. options, we love options 💖

🌈 HISTORY 🌈

the function gd_alter_affixes() appeared in GetData-0.8.0. a legend was born 👑

in GetData-0.10.0, the error return from this function changed from -1 to a negative-valued error code. glow up fr fr.

👑 SEE ALSO 👑

gd_error(3), gd_error_string(3), gd_fragment_affixes(3), gd_include_affix(3), gd_open(3), dirfile(5), dirfile-format(5)

okay that's the whole page bestie, every last detail preserved, nothing skipped, you're so welcome 💜

this was Version 0.10.0, dated 27 January 2016 — like, iconic vintage energy honestly 🦋💅✨