tdom(n)

💖 NAME 💖

tdom — okay so basically tdom is an expat parser object extension whose whole thing is building an in-memory DOM tree out of the input while it's parsing. no cap. 🦋

---

✨ SYNOPSIS ✨

package require tdom

set parser [expat]

tdom $parser enable

that's it bestie, that's the whole vibe. 🎀

---

🌸 DESCRIPTION 🌸

okay so here's the tea, fr fr: tdom adds the C handler set "tdom" to a Tcl expat parser obj. This handler set builds an in-memory DOM tree out of the input, parsed by the parser. 🧚

A DOM tree created this way behaves exactly like a DOM tree created by the dom command (see there, go look, iykyk). In fact — and this is the iconic part — tdom is only another interface to the same functionality; it uses the code behind the dom code for building the DOM tree. literally the same code, just a different door into the party. 💅

---

🫶 the methods, bestie 🫶

• tdom parserObj enable — adds the tdom C handler set to a Tcl expat parser object. Next time the parser parses input, the tdom C handler functions create an in-memory DOM tree. slay. ✨
• tdom parserObj getdoc — returns the DOM tree as a domDoc (see there) object. your tree, hand-delivered. 👑
• tdom parserObj setStoreLineColumn ?boolean? — see the method setStoreLineColumn of the dom command. same energy, different address. 🦋
• tdom parserObj remove — removes the tdom C handler set from the parser object. it's giving "we're done here". 💀
• tdom parserObj keepEmpties — see the option -keepEmpties of the dom command. 🍓
• tdom parserObj setExternalEntityResolver script — the page literally just says this and then moves on, so that's all the lore we have, bestie. no elaboration, no extras, don't come for me. 😭

---

🔥 SEE ALSO 🔥

• dom
• expat

---

👑 KEYWORDS 👑

• DOM
• SAX
• C handler set

---

and that's the whole page, periodt. this one's from the Tcl manual, page tdom(n) — go forth and build your trees. 💜🎀🦋