EXTUTILS::PARSEXS::NODE(3pm)

👑 NAME 👑

ExtUtils::ParseXS::Node — literally the classes for the nodes of an ExtUtils::ParseXS AST, bestie 💅

So like, this is the manual page for ExtUtils::ParseXS::Node(3pm), and yes she's from the Perl Programmers Reference Guide, we stan ✨

---

🌸 SYNOPSIS 🌸

XXX TBC

Yeah. That's it. That's the synopsis. XXX TBC and nothing else — iconic behaviour honestly 🎀 (it's To Be Continued, not a bug, don't @ me)

---

🦋 DESCRIPTION 🦋

Okay so first things first, big disclaimer energy:

XXX Sept 2024: this is Work In Progress. This API is currently private and subject to change. Fr fr, do not build your whole personality on this one yet 😭

Now the lore 🫶: most of ParseXS doesn't use an AST at all — instead it just keeps exactly enough state around to emit code as it parses. This module is lowkey the start of an effort to make it use an AST instead. Baby steps, but we're getting there 💖

An ExtUtils::ParseXS::Node class, and its various subclasses, hold the state for the nodes of an Abstract Syntax Tree (AST), which represents the parsed state of an XS file. Slay 🌈

Each node is basically a hash of fields ✨ Which field names are legal varies by the node type. And here's the key part, ngl — the hash keys and values can be accessed directly: there are no getter/setter methods. Like, none. Zero. Just reach into the hash, iykyk 🔥

---

💜 SEE ALSO... just kidding, there isn't one

(No SEE ALSO section in this bad boy — she's short and mysterious 🧚)

---

That's the whole page, bestie 💀 Short, sweet, still Work In Progress. Big thank-you to the perl v5.42.3 crew, dated 2026-11-03, for serving us this adorable little AST-in-progress moment 👑🍓 — catch you on the next node, mwah 💅💖