ack/klammertext
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
main
klammertext/tst/coverage/cycle.k

23 lines
908 B
Plaintext
Raw Permalink Normal View History

Target coverage: a klammer states the targets it serves kdesc gains --coverage, which reports for every klammer the set of targets it can render to, and — the point of it — which klammers' coverage cannot be derived and must therefore be declared. Three rules: coverage is DERIVED where the definitions determine it (a general body of klammer calls covers the intersection of what those klammers cover, by a greatest fixpoint after loading), DECLARED where the engine cannot interpret what decides it (an @eval body, whose targets are undecidable), and UNKNOWN where nothing is written — which never means "deliberately unavailable". Two new spellings in a definition's name. A comma-separated target list, "@@table.html,tex :: ...", gives one body several targets; it is surface syntax, expanded at registration, and each member goes through the redefinition rules on its own. And "@@date.* :: ..." writes the general target out, asserting that the klammer works for EVERY target including ones not yet defined — a stronger claim than a list of the targets defined today, and the one target declaration that could be mechanically falsified. The Standard Klammer Set was swept accordingly: it now has no general definitions at all, every klammer names the targets it serves, six use ".*", and tex and pdf are at zero undecided. kdesc's flags are reorganised on two rules: a flag reached for often gets a single letter (-k klammers, -t targets, -c characters, -i input), a more specialised topic a multi-letter name (--argtypes, --katoms, --rewrite, --optionsets, --coverage, --klammerset, --font); and -v says how much to show about PROCESSING, never what the RESULT contains — so the katom regex column is "--katoms full" and the coverage detail "--coverage all". NOTE: "-k" now lists klammers (optionally filtered by a name/description search); the katom table moved to "--katoms". Fixes carried along: an option written with no value crashed the command with SIGSEGV instead of reporting the mistake; two required positional arguments never parsed; kdesc and kdiag printed an error and exited 0; and definition diagnostics counted registrations rather than what was written, so one line could be reported as two definitions and then printed twice. Four new test suites: target_list, coverage, command_option, kdesc. (from dev 46f54080bd9a)
2026-08-12 17:20:23 +02:00
@@@target ta | Target A @@@
@@@target tb | Target B @@@
# Mutual reference between two general klammers. A recursive analysis would
# not terminate; the greatest fixpoint does.
#
# These take a parameter deliberately. A general klammer with NO parameters
# is a CONSTANT, and a constant's body is spliced into later definitions at
# definition time -- so a parameterless pair never reaches the fixpoint as a
# cycle: the expansion has already turned the second body into a
# self-reference. Parameters keep the calls in the stored body.
@@ping s : @pong *s* @ @@
@@pong s : @ping *s* @ @@
# A cycle that reaches a constrained klammer keeps the constraint.
@@only_ta.ta s : A*s* @@
@@loop_a s : @loop_b *s* @ @only_ta *s* @ @@
@@loop_b s : @loop_a *s* @ @@
# Disjoint coverage: nothing is in both, so this can never be applied.
@@only_tb.tb s : B*s* @@
@@impossible s : @only_ta *s* @ @only_tb *s* @ @@
Reference in New Issue Copy Permalink