pt_export_api(3tcl)

📦
version 2.0 · 2 versions
, in debian trixie, ubuntu questing, ubuntu resolute, ubuntu stonking

✨ pt_export_api — Parser Tools Export API ✨

okay bestie, welcome to the manual page for pt_export_api, living under the 3tcl umbrella in the Parser Tools fam. this one is the whole export API situation, so grab a snack 🍓

🌸 SYNOPSIS 🌸

package require Tcl 8.5 9

CONVERTER reset

CONVERTER configure

CONVERTER configure option

CONVERTER configure option value...

CONVERTER convert serial

::export serial configuration

💖 DESCRIPTION 💖

okay so, real talk: are you lost? 😭 are you having trouble understanding this document? if that's you, please go read the overview provided by the Introduction to Parser Tools. this document right here is literally the entrypoint to the whole system that the current package is a part of, so it's kind of a big deal 💅

so this doc describes two APIs. first up: the API that every package shares for converting Parsing Expression Grammars into some other format. and then second: the API shared by the packages that implement the export plugins sitting on top of those conversion packages. two APIs, one page, iconic 🫶

its intended audience? the girlies who wish to create their own converter for some type of output, and/or an export plugin for their own or for some other converter. if that's you, hi, this is for you ✨

it resides in the Export section of the Core Layer of Parser Tools.

IMAGE: arch_core_export

👑 CONVERTER API 👑

any (grammar) export converter has to follow the rules set out below, no skipping, no shortcuts:

  1. a converter is a package. its name is arbitrary, however it is recommended to put it under the ::pt::peg::to namespace.
  2. the package provides either a single Tcl command following the API outlined below, or a class command whose instances follow that same API. the commands which follow the API are called converter commands.
  3. a converter command has to provide the following three methods with the given signatures and semantics. converter commands are allowed to provide more methods of their own, but not less, and they may not provide different semantics for the standardized methods. no cap.
    • CONVERTER reset — this method has to reset the configuration of the converter to its default settings. the result of the method has to be the empty string. clean slate energy 🌈
    • CONVERTER configure — this method, in this form, has to return a dictionary containing the current configuration of the converter. like a little mirror of its soul 💖
    • CONVERTER configure option — this method, in this form, has to return the current value of the specified configuration option of the converter.

please read the section Options for the set of standard options any converter has to accept. any other options accepted by a specific converter will be described in its manpage. iykyk.

  • CONVERTER configure option value... — this command, in this form, sets the specified options of the converter to the given values.

please read the section Options for the set of standard options a converter has to accept. any other options accepted by a specific converter will be described in its manpage.

  • CONVERTER convert serial — this method has to accept the canonical serialization of a parsing expression grammar, as specified in section PEG serialization format, and contained in serial. the result of the method has to be the result of converting the input grammar into whatever the converter is for, per its configuration. it's giving transformation ✨🦋

🎀 PLUGIN API 🎀

any (grammar) export plugin has to follow the rules set out below:

  1. a plugin is a package.
  2. the name of a plugin package has the form pt::peg::export::FOO, where FOO is the name of the format the plugin will generate output for.
  3. the plugin can expect that the package pt::peg::export::plugin is present, as indicator that it was invoked from a genuine plugin manager.

it is recommended that a plugin does check for the presence of this package. vibe check those imports, bestie 🔥

  1. a plugin has to provide a single command, in the global namespace, with the signature shown below. plugins are allowed to provide more command of their own, but not less, and they may not provide different semantics for the standardized command.
    • ::export serial configuration — this command has to accept the canonical serialization of a parsing expression grammar and the configuration for the converter invoked by the plugin. the result of the command has to be the result of the converter invoked by the plugin for th input grammar and configuration.
      • string serial — this argument will contain the canonical serialization of the parsing expression grammar for which to generate the output. the specification of what a canonical serialization is can be found in the section PEG serialization format.
      • dictionary configuration — this argument will contain the configuration to configure the converter with before invoking it, as a dictionary mapping from options to values.

please read the section Options for the set of standard options any converter has to accept, and thus any plugin as well. any other options accepted by a specific plugin will be described in its manpage.

  1. a single usage cycle of a plugin consists of an invokation of the command export. this call has to leave the plugin in a state where another usage cycle can be run without problems. reusability? we love to see it 💅

💜 OPTIONS 💜

each export converter and plugin for an export converter has to accept the options below in their configure method. converters are allowed to ignore the contents of these options when performing a conversion, but they must not reject them. plugins are expected to pass the options given to them to the converter they are invoking.

  • -file string — the value of this option is the name of the file or other entity from which the grammar came, for which the command is run. the default value is unknown.
  • -name string — the value of this option is the name of the grammar we are processing. the default value is a_pe_grammar.
  • -user string — the value of this option is the name of the user for which the command is run. the default value is unknown.

🌈 USAGE 🌈

to use a converter do

# Get the converter (single command here, not class)
package require the-converter-package

# Provide a configuration
theconverter configure ...

# Perform the conversion
set result [theconverter convert $thegrammarserial]

... process the result ...

to use a plugin FOO do

# Get an export plugin manager
package require pt::peg::export
pt::peg::export E

# Provide a configuration
E configuration set ...

# Run the plugin, and the converter inside.
set result [E export serial $grammarserial FOO]

... process the result ...

✨ PEG SERIALIZATION FORMAT ✨

okay bestie, listen up, because this section is literally the blueprint 📜💖 Here we're specifying the format the Parser Tools use to serialize Parsing Expression Grammars as immutable values — you know, for transport, for comparison, for all the vibes. 🦋

And there are two flavors: regular and canonical. A PEG can have many regular serializations, but only exactly one of them is canonical. One. Single. Queen. 👑

🌸 regular serialization 🌸

  1. The serialization of any PEG is a nested Tcl dictionary. nesting doll energy 🪆
  2. This dictionary holds a single key, pt::grammar::peg, and its value. That value holds the contents of the grammar.
  3. The contents of the grammar are a Tcl dictionary holding the set of nonterminal symbols and the starting expression. The relevant keys and their values are:
    • rules — The value is a Tcl dictionary whose keys are the names of the nonterminal symbols known to the grammar. 📚
      1. Each nonterminal symbol may occur only once. no duplicates allowed, this isn't a group chat with double-texters 🙅‍♀️
      2. The empty string is not a legal nonterminal symbol. "" is NOT it, bestie.
      3. The value for each symbol is a Tcl dictionary itself. The relevant keys and their values in this dictionary are:
        • is — The value is the serialization of the parsing expression describing the symbol's sentential structure, as specified in the section PE serialization format. 🎀
        • mode — The value can be one of three values specifying how a parser should handle the semantic value produced by the symbol.
          • value — The semantic value of the nonterminal symbol is an abstract syntax tree consisting of a single node node for the nonterminal itself, which has the ASTs of the symbol's right hand side as its children. full family tree, so wholesome 🫶
          • leaf — The semantic value of the nonterminal symbol is an abstract syntax tree consisting of a single node node for the nonterminal, without any children. Any ASTs generated by the symbol's right hand side are discarded. bye bye children 👋
          • void — The nonterminal has no semantic value. Any ASTs generated by the symbol's right hand side are discarded (as well). nothing to see here, literally 💀
    • start — The value is the serialization of the start parsing expression of the grammar, as specified in the section PE serialization format. the main character of the grammar, fr fr 👑
  4. The terminal symbols of the grammar are specified implicitly as the set of all terminal symbols used in the start expression and on the RHS of the grammar rules. no list needed, they just show up and slay ✨

💅 canonical serialization 💅

The canonical serialization of a grammar has the format as specified in the previous item, and then additionally satisfies the constraints below, which make it unique among all the possible serializations of this grammar. yes, unique. one of one. 💖

  1. The keys found in all the nested Tcl dictionaries are sorted in ascending dictionary order, as generated by Tcl's builtin command lsort -increasing -dict. alphabetize or perish 📖
  2. The string representation of the value is the canonical representation of a Tcl dictionary. I.e. it does not contain superfluous whitespace. no extra spaces, we are not messy here 🧹

🌈 EXAMPLE 🌈

Assuming the following PEG for simple mathematical expressions:

PEG calculator (Expression)
    Digit      <- '0'/'1'/'2'/'3'/'4'/'5'/'6'/'7'/'8'/'9'       ;
    Sign       <- '-' / '+'                                     ;
    Number     <- Sign? Digit+                                  ;
    Expression <- Term (AddOp Term)*                            ;
    MulOp      <- '*' / '/'                                     ;
    Term       <- Factor (MulOp Factor)*                        ;
    AddOp      <- '+'/'-'                                       ;
    Factor     <- '(' Expression ')' / Number                   ;
END;

then its canonical serialization (except for whitespace) is:

pt::grammar::peg {
    rules {
        AddOp      {is {/ {t -} {t +}}                                                                mode value}
        Digit      {is {/ {t 0} {t 1} {t 2} {t 3} {t 4} {t 5} {t 6} {t 7} {t 8} {t 9}}                mode value}
        Expression {is {x {n Term} {* {x {n AddOp} {n Term}}}}                                        mode value}
        Factor     {is {/ {x {t (} {n Expression} {t )}} {n Number}}                                  mode value}
        MulOp      {is {/ {t *} {t /}}                                                                mode value}
        Number     {is {x {? {n Sign}} {+ {n Digit}}}                                                 mode value}
        Sign       {is {/ {t -} {t +}}                                                                mode value}
        Term       {is {x {n Factor} {* {x {n MulOp} {n Factor}}}}                                    mode value}
    }
    start {n Expression}
}

look at that clean, sorted, whitespace-disciplined masterpiece 😭✨ she's beautiful, your honor.

PE SERIALIZATION FORMAT

okay bestie, this is the section where we spill exactly how the Parser Tools write Parsing Expressions down as immutable values — for shipping them around, comparing them, all that 💅

We distinguish between regular and canonical serializations. A parsing expression can have more than one regular serialization, but exactly one of them will be canonical. one. singular. no cap. 👑

Regular serialization

Atomic Parsing Expressions

  1. The string epsilon is an atomic parsing expression. It matches the empty string. (matching literally nothing is a vibe 🌸)
  2. The string dot is an atomic parsing expression. It matches any character.
  3. The string alnum is an atomic parsing expression. It matches any Unicode alphabet or digit character. This is a custom extension of PEs based on Tcl's builtin command string is.
  4. The string alpha is an atomic parsing expression. It matches any Unicode alphabet character. This is a custom extension of PEs based on Tcl's builtin command string is.
  5. The string ascii is an atomic parsing expression. It matches any Unicode character below U0080. This is a custom extension of PEs based on Tcl's builtin command string is.
  6. The string control is an atomic parsing expression. It matches any Unicode control character. This is a custom extension of PEs based on Tcl's builtin command string is.
  7. The string digit is an atomic parsing expression. It matches any Unicode digit character. heads up: this includes characters outside of the [0..9] range. This is a custom extension of PEs based on Tcl's builtin command string is.
  8. The string graph is an atomic parsing expression. It matches any Unicode printing character, except for space. This is a custom extension of PEs based on Tcl's builtin command string is.
  9. The string lower is an atomic parsing expression. It matches any Unicode lower-case alphabet character. This is a custom extension of PEs based on Tcl's builtin command string is.
  10. The string print is an atomic parsing expression. It matches any Unicode printing character, including space. This is a custom extension of PEs based on Tcl's builtin command string is.
  11. The string punct is an atomic parsing expression. It matches any Unicode punctuation character. This is a custom extension of PEs based on Tcl's builtin command string is.
  12. The string space is an atomic parsing expression. It matches any Unicode space character. This is a custom extension of PEs based on Tcl's builtin command string is.
  13. The string upper is an atomic parsing expression. It matches any Unicode upper-case alphabet character. This is a custom extension of PEs based on Tcl's builtin command string is.
  14. The string wordchar is an atomic parsing expression. It matches any Unicode word character. That's any alphanumeric character (see alnum), plus any connector punctuation characters (e.g. underscore). This is a custom extension of PEs based on Tcl's builtin command string is.
  15. The string xdigit is an atomic parsing expression. It matches any hexadecimal digit character. This is a custom extension of PEs based on Tcl's builtin command string is.
  16. The string ddigit is an atomic parsing expression. It matches any decimal digit character. This is a custom extension of PEs based on Tcl's builtin command regexp.
  17. The expression [list t x] is an atomic parsing expression. It matches the terminal string x.
  18. The expression [list n A] is an atomic parsing expression. It matches the nonterminal A.

Combined Parsing Expressions

  1. For parsing expressions e1, e2, ... the result of [list / e1 e2 ... ] is a parsing expression as well. This is the ordered choice, aka prioritized choice.
  2. For parsing expressions e1, e2, ... the result of [list x e1 e2 ... ] is a parsing expression as well. This is the sequence.
  3. For a parsing expression e the result of [list * e] is a parsing expression as well. This is the kleene closure, describing zero or more repetitions.
  4. For a parsing expression e the result of [list + e] is a parsing expression as well. This is the positive kleene closure, describing one or more repetitions.
  5. For a parsing expression e the result of [list & e] is a parsing expression as well. This is the and lookahead predicate.
  6. For a parsing expression e the result of [list ! e] is a parsing expression as well. This is the not lookahead predicate.
  7. For a parsing expression e the result of [list ? e] is a parsing expression as well. This is the optional input.

Canonical serialization

The canonical serialization of a parsing expression has the format as specified in the previous item, and then additionally satisfies the constraints below, which make it unique among all the possible serializations of this parsing expression. she's the main character, fr fr ✨

  1. The string representation of the value is the canonical representation of a pure Tcl list. I.e. it does not contain superfluous whitespace.
  2. Terminals are not encoded as ranges (where start and end of the range are identical).

EXAMPLE

Assuming the parsing expression shown on the right-hand side of the rule

Expression <- Term (AddOp Term)*

then its canonical serialization (except for whitespace) is

{x {n Term} {* {x {n AddOp} {n Term}}}}

look at her go 😭💖

BUGS, IDEAS, FEEDBACK

bestie, real talk: 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 package and/or documentation. we want the glow-up 🫶

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

Also, 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

CATEGORY

Parsing and Grammars 🦋

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

and that's a wrap on the whole page, babe 🎀 she's pt_export_api(3tcl), she ships with tcllib at version 1.1, and that's the footer energy — go forth and serialize your parsing expressions canonically, you absolute icon 👑✨

📦 where this page comes from