tdom(3tcl)

okay so bestie, welcome to tdom(3tcl) — it's giving expat parser object extension, and it's here to build an in-memory DOM tree while parsing. No cap. 💅✨

✨ NAME ✨

tdom — it's an expat parser object extension to create an in-memory DOM tree from the input while parsing. That's the whole main character energy right there. 🌈🦋

🎀 SYNOPSIS 🎀

package require tdom

set parser [expat]

tdom $parser enable

🌸 DESCRIPTION 🌸

tdom adds the C handler set "tdom" to an 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 behave exactly like a DOM tree created by the "dom" command (see there). In fact, tdom is only another interface to the same functionality; it uses the code behind the dom code for building the DOM tree. Periodt. 💖

Here's the subcommand lineup, 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. 🔥
• tdom parserObj getdoc — Returns the DOM tree as domDoc (see there) object. 👑
• tdom parserObj setStoreLineColumn ?boolean? — See the method setStoreLineColumn of the dom command. 🎀
• tdom parserObj remove — Removes the tdom C handler set from the parser object. 🧹
• tdom parserObj keepEmpties — See the option -keepEmpties of the dom command. 🌸
• tdom parserObj setExternalEntityResolver script — the original page doesn't describe this one, so I'm not gonna make anything up. It's just listed, exactly like this. 💀🫶

🦋 SEE ALSO 🦋

dom, expat

👑 KEYWORDS 👑

DOM, SAX, C handler set

And that's the footer tea: source is Tcl, manual is tdom(3tcl) — no date on this one, so I'm not inventing one. Byeeee, go parse something cute. 💖✨🎀