KJSON_OBJ_OPEN(3)

πŸ“¦ version 1.0.1, in alpine 3.24

πŸ’– KJSON_OBJ_OPEN(3) πŸ’–

okay so this is the KJSON_OBJ_OPEN(3) page from the Library Functions Manual, and bestie, it's lowkey a whole moment. it's about opening object scopes for kcgijson β€” come get your JSON nesting situation going ✨

🌸 NAME 🌸

kjson_obj_open, kjson_objp_open β€” open object scope for kcgijson (yes bestie, that's the whole name vibe πŸ’…)

πŸ¦‹ LIBRARY πŸ¦‹

library β€œlibkcgijson” β€” that's where this little icon lives 🫢

✨ SYNOPSIS ✨

drop these includes first, then pick your function:

#include <sys/types.h>
#include <stdarg.h>
#include <stdint.h>
#include <kcgi.h>
#include <kcgijson.h>

enum kcgi_err
kjson_obj_open(struct kjsonreq *req);

enum kcgi_err
kjson_objp_open(struct kjsonreq *req, const char *name);

πŸŽ€ DESCRIPTION πŸŽ€

Open an object scope in a context req initialised with khtml_open(3). Scopes are closed with kjson_obj_close(3) or kjson_close(3). Object scopes may be filled in with further named pairs as with kjson_putstringp(3).

The kjson_obj_open() form is for array scopes, while kjson_objp_open() is for objects.

Passing a NULL value to name for kjson_objp_open() is equivalent to calling kjson_obj_open().

πŸ’œ RETURN VALUES πŸ’œ

Returns an enum kcgi_err indicating the error state. vibe check time:

  • KCGI_OK β€” success, and no cap it's not an error πŸŽ€
  • KCGI_ENOMEM β€” internal memory allocation failure, including reaching the maximum number of possible JSON scopes πŸ’€
  • KCGI_HUP β€” the output connection has been terminated. For FastCGI connections, the current connection should be released with khttp_free(3) and parse loop reentered 😭
  • KCGI_FORM β€” the connection is still expecting headers with khttp_head(3). Indicates that khttp_body(3) did not return with success or was not invoked. For FastCGI connections, the current connection should be released with khttp_free(3) and parse loop reentered 🫠
  • KCGI_SYSTEM β€” internal system error writing to the output stream 😡
  • KCGI_WRITER β€” the incorrect form was used for the current scope, for example, an array-type write within an object. it's giving wrong-scope energy, fr fr 🚩

πŸ”₯ EXAMPLES πŸ”₯

The following outputs a simple JSON document. It assumes r is a struct kreq pointer. For brevity, it does not do any error checking.

khttp_head(r, kresps[KRESP_STATUS],
  "%s", khttps[KHTTP_200]);
khttp_head(r, kresps[KRESP_CONTENT_TYPE],
  "%s", kmimetypes[KMIME_APP_JSON]);
khttp_body(r);
kjson_open(&req, r);
kjson_obj_open(&req);
kjson_putstringp(&req, "bar", "shbar");
kjson_arrayp_open(&req, "baz");
kjson_putstring(&req, "xyzzy"));
kjson_close(&req);

🌈 SEE ALSO 🌈

kcgijson(3) β€” go peek at the parent page, iykyk πŸ‘‘

πŸ‘‘ AUTHORS πŸ‘‘

Written by Kristaps Dzonsons <kristaps@bsd.lv>.


okay that's the whole page, bestie 🫢 β€” source Debian, footer date stamp $Mdocdate$, and this is KJSON_OBJ_OPEN(3) signing off. periodt πŸ’‹

πŸ“¦ where this page comes from
  • alpine 3.24: kcgi-doc 1.0.1-r0 Β· ISC
  • πŸ’– girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms