pt::tclparam:...ration::tcloo(n)

💖 pt::tclparam::configuration::tcloo 💖

okay bestie, so this whole thing lives in the Parser Tools manual, and it's the page for pt::tclparam::configuration::tcloo. yes the name is a whole mouthful. no we're not changing it. it's iconic like that. 🎀

---

✨ NAME ✨

pt::tclparam::configuration::tcloo — Tcl/PARAM, Canned configuration, Tcloo

like... that's literally it. canned config. Tcloo flavored. slay.

---

🌸 SYNOPSIS 🌸

package require Tcl 8.5 9

package require pt::tclparam::configuration::tcloo ?1.0.5?

::pt::tclparam::configuration::tcloo def name pkg version cmdprefix

the ?1.0.5? is giving "optional, but the vibe is 1.0.5". periodt.

---

🦋 DESCRIPTION 🦋

Are you lost ? Do you have trouble understanding this document ? 💀 bestie if that's you, no shame, go read the overview in the Introduction to Parser Tools first. that doc is the entrypoint to the whole system that this current package is a part of. it's the main character of the docs, fr fr.

so here's the tea: this package is an adjunct to pt::peg::to::tclparam. the whole point is that pt::peg::to::tclparam is highly configurable — like, so configurable — and this package makes using it easier by handing you a canned configuration. 🥫✨ when you apply this configuration, it causes pt::peg::to::tclparam to generate OO-based parser packages. that's the whole job. that's the assignment. and it ate.

it's a supporting package in the Core Layer of Parser Tools.

IMAGE: arch_core_support

---

👑 API 👑

• ::pt::tclparam::configuration::tcloo def name pkg version cmdprefix — the command that applies the configuration provided by this package to the cmdprefix, causing the creation of OO-based parsers whose class is name, in package pkg with version. 🫶

the use of a command prefix as API is lowkey genius because it lets you apply the configuration to not only pt::peg::to::tclparam (that's pt::peg::to::tclparam configure), but also to export manager instances and PEG containers (that's $export configuration set and [$container exporter] configuration set respectively). multi-purpose. we love to see it.

or, honestly, anything other command prefix accepting two arguments, option and value. that's the requirement. two args. option and value. no more, no less. 💅

---

💀 BUGS, IDEAS, FEEDBACK 💀

This document, and the package it describes, will undoubtedly contain bugs and other problems.

ngl the original said it first, not me. 😭 please report such in the category pt of the Tcllib Trackers at [http://core.tcl.tk/tcllib/reportlist]. and please also report any ideas for enhancements you may have for either the package and/or the documentation. we want the ideas. give us the ideas. 🧚

when proposing code changes, please provide unified diffs, i.e the output of diff -u. exact words, bestie.

note further that attachments are strongly preferred over inlined patches. 🔥 attachments can be made by going to the Edit form of the ticket immediately after its creation, and then using the left-most button in the secondary navigation bar. iykyk.

---

🍓 KEYWORDS 🍓

EBNF, LL(k), PEG, TDPL, context-free languages, expression, grammar, matching, parser, parsing expression, parsing expression grammar, push down automaton, recursive descent, state, top-down parsing languages, transducer

look at that list. it's giving syllabus. it's giving "i know what all of these mean and you will too". 🌈

---

💜 CATEGORY 💜

Parsing and Grammars

---

🎀 COPYRIGHT 🎀

Copyright (c) 2009 Andreas Kupries <andreas_kupries@users.sourceforge.net>

---

and that's the page!! 💖 this was tcllib, version 1.0.5, from the Parser Tools corner of the world, and you just read the whole thing. so proud of you. go generate some OO-based parsers. 🦋✨👑