From a7dab091503d997490434372c8fc3eabd9c8eb09 Mon Sep 17 00:00:00 2001 From: Brad Arant Date: Wed, 26 Aug 2026 09:18:24 -0700 Subject: [PATCH] Add DEFINED TAGS listing to output Custom definitions have no scope levels the way variables do - __tag.cpp always registers into the single global.tags map regardless of where in the script the definition sits, so this is one flat list, not broken out by global/local/parent like the existing variable/keyword sections. Verified end-to-end via a real jet-2.0 run: two tags defined before both appear correctly in the DEFINED TAGS section. --- __dump.cpp | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/__dump.cpp b/__dump.cpp index 45b5862..7ef143f 100644 --- a/__dump.cpp +++ b/__dump.cpp @@ -29,10 +29,19 @@ namespace jet { for (auto i = parent->keywords.begin(); i != parent->keywords.end(); i++) outFile << i->first << "=[" << i->second << "]" << std::endl; - outFile << "*** COOKIES ***" << std::endl; + outFile << "*** COOKIES ***" << std::endl; for (auto i = global.cookies.data.begin(); i != global.cookies.data.end(); i++) outFile << i->first << "=[" << i->second << "]" << std::endl; + // Unlike variables (which have real global/local/parent scoping), + // custom definitions have only one level - __tag.cpp + // always registers into global.tags regardless of where in the + // script the definition sits, so there's nothing to break out by + // scope here. + outFile << "*** DEFINED TAGS ***" << std::endl; + for (auto i = global.tags.begin(); i != global.tags.end(); i++) + outFile << i->first << std::endl; + outFile.close(); }