gd_entry_type(3)

💖 gd_entry_type(3) — the GETDATA glow-up 💖

okay bestie, pull up a chair because we're about to find out exactly what kind of field you're dealing with, and honestly? it's giving detective energy 🕵️♀️✨

✨ NAME ✨

gd_entry_type — retrieve the type of a dirfile field 💅

🎀 SYNOPSIS 🎀

#include <getdata.h>

gd_entype_t gd_entry_type(const DIRFILE *dirfile, const char *field_code);

🦋 DESCRIPTION 🦋

so like, the gd_entry_type() function slides into a dirfile(5) database — that's the one you passed in as dirfile — and it's gonna tell you the field type of whatever field you named in field_code. no cap, that's the whole vibe. 🌸

and here's a lil detail that matters: if field_code has a valid representation suffix on it, bestie, it gets ignored. like, completely. don't even worry about it, it's not invited to the party. 🙈

now, the gd_entype_t type? it's an enumerated type, which is fancy speak for "it can only be one of these specific things." and the things are:

GD_BIT_ENTRY, GD_CARRAY_ENTRY, GD_CONST_ENTRY, GD_DIVIDE_ENTRY,
GD_INDEX_ENTRY, GD_INDIR_ENTRY, GD_LINCOM_ENTRY,
GD_LINTERP_ENTRY, GD_MPLEX_ENTRY, GD_MULTIPLY_ENTRY,
GD_PHASE_ENTRY, GD_POLYNOM_ENTRY, GD_RAW_ENTRY, GD_RECIP_ENTRY,
GD_SARRAY_ENTRY, GD_SBIT_ENTRY, GD_SINDIR_ENTRY, GD_STRING_ENTRY,
GD_WINDOW_ENTRY.

nineteen little icons, all with main character energy. it's giving a whole roster. 👑

💜 RETURN VALUE 💜

when everything goes right? gd_entry_type() hands you the field type of the field you asked about. iconic. slay. 🫶

but when it goes wrong — and bestie, sometimes it goes wrong — gd_entry_type() returns GD_NO_ENTRY and tucks a negative-valued error code into the DIRFILE object. you can get that lil guy back later by calling gd_error(3). the possible error codes are:

• GD_E_BAD_DIRFILE — the dirfile you handed over was invalid. not it. 💀
• GD_E_BAD_CODE — the field you named in field_code? not found in the database. it's simply not there, fr fr. 😭

and if you want an actual descriptive error string instead of just a code, go call gd_error_string(3). she'll explain everything. 🌈

🌟 HISTORY 🌟

the get_entry_type() function first appeared in GetData-0.5.0. throwback era.

then in GetData-0.7.0, it got renamed to gd_entry_type(). glow-up complete, new name, same energy. ✨

👑 SEE ALSO 👑

• gd_entry(3)
• gd_error(3)
• gd_error_string(3)
• gd_fragmentname(3)
• gd_open(3)
• gd_parent_fragment(3)
• dirfile(5)

and that's the whole page, bestie!! 💖 this was Version 0.10.0, dated 25 December 2016 — a lil holiday gift from the GETDATA manual, gd_entry_type(3) section. go forth and type-check those fields, you absolute legend. 🎀🦋🌸💅