PT_TCLPARAM_CONFIG_NX(n)

💖 pt::tclparam::configuration::nx — the manual page, bestie edition 💖

okay so. welcome to the pt::tclparam::configuration::nx page, part of the Parser Tools situation. it's giving "canned configuration" and honestly? iconic. let's get into it 🫶

---

✨ NAME ✨

pt::tclparam::configuration::nx — Tcl/PARAM, Canned configuration, NX

like. that's the whole vibe. a canned config. for NX. for Tcl/PARAM. periodt 💅

---

🌸 SYNOPSIS 🌸

package require Tcl 8.5 9

package require pt::tclparam::configuration::nx ?1.0.2?

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

so you need Tcl 8.5 or 9 (yes, both, she's flexible), and the package itself which is optionally version 1.0.2 — the ? ? around it means "you can pin it if you want, no pressure bestie".

---

🦋 DESCRIPTION 🦋

Are you lost? Do you have trouble understanding this document? 😭 In that case, please read the overview provided by the Introduction to Parser Tools. That document is literally the entrypoint to the whole system that this current package is a part of. no cap.

This package is an adjunct to pt::peg::to::tclparam, and its whole job is to make that highly configurable package easier to use by handing you a canned configuration. When it gets applied, this configuration causes pt::peg::to::tclparam to generate NX-based parser packages. slay.

It is a supporting package in the Core Layer of Parser Tools. supporting character but honestly? main character energy.

IMAGE: arch_core_support

---

👑 API 👑

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

The use of a command prefix as the API is what makes this so versatile bestie — it allows application of the configuration to not only:

• pt::peg::to::tclparam (via pt::peg::to::tclparam configure)

but also to export manager instances and PEG containers, using $export configuration set and [$container exporter] configuration set respectively.

Or literally anything else that's a command prefix accepting two arguments: option and value. the way that it just works with anything? obsessed. 💖

---

💀 BUGS, IDEAS, FEEDBACK 💀

This document, and the package it describes, will undoubtedly contain bugs and other problems. 🙈 Please report such in the category pt of the Tcllib Trackers [http://core.tcl.tk/tcllib/reportlist]. Please also report any ideas for enhancements you may have for either the package and/or the documentation.

When proposing code changes, please provide unified diffs, i.e. the output of diff -u.

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

(that's a lot of keywords and every single one of them ate, fr fr 🔥)

---

🌈 CATEGORY 🌈

Parsing and Grammars

---

🧚 COPYRIGHT 🧚

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

---

and that's the whole page bestie!! this was tcllib, version 1.0.2, and the page you just read is pt::tclparam::configuration::nx(n). go build some NX-based parsers, you've got this 💜✨🎀