Tcl 2016 Conference, Houston/TX, US, Nov 14-18
Send your abstracts to by Sep 12.

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

50 most recent timeline items

22:24 • Ticket [186c6e23bf] match state - expose more of events - listing, on/off status still Open with 3 other changes (user: aku)
22:22 • Ticket [b10e687636] Create sample parser for SQL ISO standard status still Open with 3 other changes (user: aku)
[7337a35e08] Leaf: Merge staging into main stream. Basic parse events (io, lexer) done. Basic input extension done. Doctools example working (macros, includes) json blocked out (issues with partial utf, non-utf, non-standard codings - Tcl vs. C pre-handling, strings vs. file) (user: aku, tags: trunk)
[15feed5264] Closed-Leaf: Extended multi-byte char counting test to full unicode range. (user: aku, tags: trunk-stage)
[d336725a4a] Fix trailing whitespace (user: aku, tags: trunk-stage)
[44fee72091] Fixed miscounting of multi-byte characters in rtC. Reworked `inbound_step()`. Changec to test a character for correctness on the first byte, then arrange to (not) step the character location on the trailer bytes following, if any. Always steps the character location on the first byte. Updates the byte/char index the same time. Further reworked and fixed the interface from `gate` to `inbound` for rewinding after a rejection (straight end, or when the matched lexeme is actually shorter than the number of bytes consumed before stopping). The used API (`moveby`) was character based, which caused us to rewind to far, namely to the previous character. No trouble when it was a single-byte character. Bad for a multi-byte however. This could then trip the lexer if the first byte of the previous character is not acceptable at the given point. (user: aku, tags: trunk-stage)
[9337c00616] Added test demonstrating that rtC miscounts multi-byte character locations (because counting at end). Added tools to help with generation of test input (user: aku, tags: trunk-stage)
[1694246f20] Tweaked test parser gen to leave a log file behind on grammar parse failure (user: aku, tags: trunk-stage)
[e64b244e12] Trim trailing whitespace (user: aku, tags: trunk-stage)
22:25 • New ticket [2062bdb5d5] marpa::unicode - change confusing command names. (user: aku)
[8b8a1cedf6] Leaf: Added runtime tests. Note: These look to need some of the fixes on trunk-stage. (user: andreask, tags: non-utf-bytes)
[2d87d5c92b] Started implementation of non-utf byte support. (user: andreask, tags: non-utf-bytes)
06:04 • New ticket [dabc3ce88c] tests - add case with ltm-mode symbols => always-on, different from discards. (user: aku)
06:03 • New ticket [2b73c9fe19] tests - add case without any discard/ltm symbols => no always-on symbols. (user: aku)
[cd54178989] Fixed mindt|doctools crashes. Two for asserts. Problem with `mindt` was in the new `gather_events` function. It was not fully adapted to the changed data structures, with the split trigger and event arrays. It saved the loop index as event id, which was correct for the old structures. With the new structures OTOH the event id is a field in the array we iterate over instead. Problem with `doctools` was as above, plus also an unknown mismanagement of the `always` array by the shared rtC generator code for LTM-mode lexemes, i.e LATM=false. It triggered a similar assertion on lexer setup after the fix above was applied. `mindt` avoided that issue because it did not use LTM-mode lexemes for its special forms. Reactivated the disabled tests. Passing now. Note: json still disabled. (user: aku, tags: trunk-stage)
[cba29d80fc] Integrated doctools example - tests - remeta Regenerated doctools example parser to match runtime changes. Disabled tests with known problems - json (char mislocation) - mindt (crash! (rtc, mis-capacity for some symset)) - doctools (crash! (rtc, mis-capacity for some symset)) (user: aku, tags: trunk-stage)
[ecf881268e] Integrate base event work. Stage before true merge. (user: aku, tags: trunk-stage)
[77d4610d6a] Closed-Leaf: Integrate base doctools example. (user: aku, tags: parse-events)
[d912ded2f3] Closed-Leaf: Brought trunk and event work. (user: aku, tags: language-doctools)
[6ceda1b56e] Brought trunk work (user: aku, tags: parse-events)
21:50 • Ticket [fca2fa991a] example doctools - testsuite - extend/fill status still Open with 4 other changes (user: aku) ... 1 similar event omitted.
21:43 • Closed ticket [d9b47bbb78]: grammar events - wrongly treating single event linked to multiple lexemes as separate/different plus 4 other changes (user: aku)
[f97a8147f6] Tkt [d9b47bbb78] completed (user: aku, tags: parse-events)
[a48220cd05] Bring in the extended test suite which runs the example tests too. (user: aku, tags: trunk)
09:04 • Edit [26a81da80592b041|26a81da805]: Edit check-in comment. (user: aku)
[26a81da805] Closed-Leaf: More integration of the language examples into the main - Run example tests with the main - Regenerate example parsers with the main parsers Updated a few tests. Note: json tests have issues. Parse location differences. Investigate. Tracked the location differences to commit [dd2dfa9d07530d8d] where definition of lexeme start switched from byte-based LEX_START to character-based LEX_START_C. This commit is on branch [parse-events-rtc]. I suspect that the stepping of character locations is incorrect. Looking at the `step()` function I see the character increment done for the last byte of the character. This is ok for the singletons. For multi-byte characters OTOH it looks to be too late. We should step at the first byte of a character. Complicating things, partial characters, i.e. missing trailers, unexpected trailers. json is good to find these issues, its test suite contains many of these cases. Fix will be done on new branch. This commit is not responsible, can be merged. (user: aku, tags: example-integration)
02:44 • Edit [7dbbfd79f5845a55|7dbbfd79f5]: Edit check-in comment. (user: aku)
02:43 • Edit [7dbbfd79f5845a55|7dbbfd79f5]: Move to branch mistake. Mark "Closed". (user: aku)
[67d5a8317b] Leaf: Integrated the language example tests into the main. Added the language example parsers to the `remeta` tool to ensure that they are updated after runtime API changes too, not just the system parsers. Dropped the replicated support files, redirected test suites to the main support as the only support. Note: The json example has issues, major testsuite fail. Bisect where this started and fix. - Looks to be lexeme location information differences between rtC and rtTcl. - Might be fixed in the parse-event branch. (user: andreask, tags: mistake, example-test-integration)
[7dbbfd79f5] Closed-Leaf: Fixed handling of `args` parameter in wrong#args error messages. The text is dependent on core version. -- There is more going on -- Critcl differences, Core differences -- Try later again -- (user: andreask, tags: mistake)
[e71840b49a] The code generating symbol names for literals was still subject on the exact content of the [:control:] charclass, causing differences in output depending on the version of Tcl used (seen between 8.5.18 and 8.5.19). Now ensured version-independent quoting in all the relevant places. Fixed order of conditions too. Cross-referenced these places. Regenerated the internal parsers (slif, literals). Updated tests. (user: aku, tags: trunk)
[3b692749d7] Closed-Leaf: Fix missed bogus `static const` in test results. (user: andreask, tags: tkt-d9b47bbb78-event-management)
[e2021e3ef5] Ticket [d9b47bbb78]. Fix event management in the generators. C runtime and generator updated for the new data structures. Tests updated. (user: aku, tags: tkt-d9b47bbb78-event-management)
21:42 • Ticket [b10e687636] Create sample parser for SQL ISO standard status still Open with 5 other changes (user: aku)
19:58 • Add attachment to ticket [b10e687636] (user: aku)
19:57 • New ticket [b10e687636] Create sample parser for SQL ISO standard. (user: aku)
19:13 • Ticket [7a49902291] implement g1 events (predicted, nulled, completed) status still Open with 4 other changes (user: aku)
19:13 • Ticket [52e1f740dc] factor include processing to general base class status still Open with 4 other changes (user: aku)
19:13 • Ticket [c74311e30c] match - implement exhaustion events status still Open with 4 other changes (user: aku)
19:12 • Ticket [54d2d56c67] grammar check - nested quantified rules status still Open with 3 other changes (user: aku)
19:12 • Ticket [416063bf4e] debugging - collect ambiguity statistics status still Open with 3 other changes (user: aku)
[69f8e6628c] Ticket [d9b47bbb78]. Fix event management in the generators. Tcl runtime and generator updated for the new data structures. Tests updated. C runtime tests broken. Next: C runtime and generator. (user: aku, tags: tkt-d9b47bbb78-event-management)
[5b0bdf9591] Ticket [d9b47bbb78]. Fix event management in the generators. Extended to fix the event data structures in general. - Modified container, grammar base, grammar classes - Event information split into declaration with state (events), and usage information (triggers). Events are managed in the main container class. Triggers are managed in the grammar base class. Code is common to L0 and G1. API used by the semantics is unchanged. Serialization structure changes. Event section is global. Trigger sections under L0, G1. Used a purpose-written tool to rewrite the old serializations in tests results (gcstate, gcr_*) to the new form. Reworked the SLIF generator to use the new form of serialization. Tests pass, no results changed. Fixed testsuite oops (generatec_gc(c|tcl)) not seen in trunk because everything with gc also had gc_c, etc. GC generators are ok as well. Extended testsuite to cover grammars with events. (user: andreask, tags: tkt-d9b47bbb78-event-management)
20:00 • Edit [4cd32b9b44cf3809|4cd32b9b44]: Add propagating "closed". (user: aku)
20:00 • Edit [4cd32b9b44cf3809|4cd32b9b44]: Move to branch mistake. (user: aku)
19:57 • Edit [8c77fd896a548057|8c77fd896a]: Cancel tag "mistake". (user: andreask)
19:56 • Edit [5bf97382b15e7dcf|5bf97382b1]: Mark "Closed". (user: aku)
19:55 • Edit [8c77fd896a548057|8c77fd896a]: Move to branch mistake. (user: aku)
19:55 • Edit [8c77fd896a548057|8c77fd896a]: Cancel tag "mistake". (user: aku)