Conversation

Notices

1. Adrian Cochrane (alcinnz@floss.social)'s status on Wednesday, 15-Feb-2023 05:03:19 JST Adrian Cochrane

   Continuing on with yesterday's thread studying the APIs Expect adds to TCL...

   `trap` parses flags, possibly examines current signal to get the data to return, once validated & with the list retrieved iterates over said list converting to an alternate TCL datastructure. Possibly configuring a signal handler to get it this data next time it recieves the signal in the TCL datamodel, via a background tasking checking its counters. Includes lookuptable conversions between signals & strings.

   1/4?

   • Adrian Cochrane (alcinnz@floss.social)'s status on Wednesday, 15-Feb-2023 05:24:23 JST Adrian Cochrane

     in reply to

     As for the main attractions of Expect commands...

     `expect`, `expect_user`, & `expect_tty` all (sharing the same code) interprets their args based on quantity evaluating an innerexpression, retrieves results, performs more complex argument parsing, iterates over commands & their states for deduplication, validates states, considers preparing a timeout, repeatedly reads results with handling & traversing the statemachines, compares against expected patterns of various types, & cleans up.

     2/4?

   • Adrian Cochrane (alcinnz@floss.social)'s status on Wednesday, 15-Feb-2023 05:36:54 JST Adrian Cochrane

     in reply to

     `expect_after`, `expect_before`, & `expect_background` all, sharing the same code, does a lot of similar stuff. Just without checking the output stream. `match_max` sets & validates a global (or channel-property) having retrieved channels state; as for `remove_nulls`, `parity`, & `close_on_eof`. `timestamp` puts more effort into argument parsing, retrieves the time, formats it according to the given format-string, & returns result to TCL.

     3/4!

   • Adrian Cochrane (alcinnz@floss.social)'s status on Wednesday, 15-Feb-2023 05:50:30 JST Adrian Cochrane

     in reply to

     That file also defines an optional debugging command stringifying the current state for output disabled in production builds. There's a background handler to retrieve the output data for the `expect*` commands, though a seperate file adds more infrastructure around it. Those commands also have several other support functions, including for carefully reading the resulting stream. There's a couple obsolete functions & running subcommands.

     4/4 Fin! Tomorrow: What did I miss?