EC_PNODE(3)

💖 EC_PNODE(3) 💖

okay so bestie, we're in the Libecoli Programmer's Manual and this page is literally all about ec_pnode — the one that makes an empty parsing tree. it's giving "lowkey tiny function, highkey important" and i'm obsessed 🫶

---

✨ NAME ✨

ec_pnode</purgle> — Create an empty parsing tree.

(no cap, that's the whole job. one tree, zero stuff in it. blank slate energy 🌸)

---

🎀 SYNOPSIS 🎀

#include <ecoli/parse.h>

struct ec_pnode * ec_pnode(
    const struct ec_node   *node   /* The grammar node. */
);

so you pull in <ecoli/parse.h>, then you call ec_pnode and hand it exactly one thing: node, which is a const struct ec_node * — the grammar node. that's the input, bestie 💅

---

🦋 DESCRIPTION 🦋

This function is used internally when parsing an input using a grammar tree.

fr fr, that's it. it's the backstage crew of parsing — not the main character on stage, but the whole show does not happen without it. it lives inside the machinery that walks a grammar tree while parsing your input. iykyk 👑

---

🌈 RETURN VALUE 🌈

The empty parse tree. ✨

(empty = fresh, untouched, no children, just vibes and a struct ec_pnode * 🎀)

---

🍓 SEE ALSO 🍓

okay so this is the group chat and ec_pnode is NOT texting alone. every single one of these is invited:

• ec_pnode_len(3)
• ec_pnode_get_strvec(3)
• ec_parse(3)
• ec_parse_strvec(3)
• ec_pnode_free_children(3)
• ec_pnode_get_root(3)
• ec_pnode_get_parent(3)
• ec_pnode_find_next(3)
• ec_pnode_get_first_child(3)
• ec_pnode_free(3)
• ec_pnode_dup(3)
• ec_pnode_matches(3)
• ec_pnode_dump(3)
• ec_pnode_unlink_child(3)
• ec_pnode_next(3)
• ec_pnode_del_last_child(3)
• ec_pnode_link_child(3)
• ec_pnode_count(3)
• ec_pnode_get_attrs(3)
• ec_pnode_get_last_child(3)
• ec_pnode_get_node(3)
• ec_pnode_find(3)
• ec_parse_child(3)

read them all, bestie, they're a set 💜

---

👑 COPYRIGHT 👑

Copyright (C) 2010-2026 Olivier Matz, Robin Jarry.

---

and that's the whole page, pookie 🥰 this was libecoli, dated 2026-06-11, filed under EC_PNODE(3) — slay, bye 💅✨