Expect – Writing a Tcl Extension in Only Seven Years (1997)

http://www.nist.gov/customcf/get_pdf.cfm?pub_id=821282

by michaelsbradley • 11 years ago

23 9 11 years ago

nist.gov

biomimic• 11 years ago

What's next for Tcl? I'm a fan.

michaelsbradley• 11 years ago

There's the Caius framework:

http://caiusproject.com/

I haven't spent any hands-on time with it yet, but what I've read so far is what led me to start learning more about expect, and Tcl in general. I'm looking for a robust way to test the systems I'm building with docker: machine, compose (fig), swarm, etc.

FabianBeiner• 11 years ago

Neat. I wrote TCL like 10 years ago daily, mostly for different shell scripts and Eggdrop extensions. That was fun…

zem• 11 years ago

is expect still the default tool for command line automation, or has it been superseded by something else?

zaphar• 11 years ago

I haven't seen anything else in use anywhere. I believe it's still pretty much the undisputed king.

cafard• 11 years ago

Perl has the work-alike Expect module.

ArkyBeagle• 11 years ago

I have found that simply opening sockets , pipes or serial ports and "fconfigure -translation binary -blocking 0 -buffering none" and using event driven I/O in regular Tcl to be superior. You use this same pattern for all activity, which makes things more consistent.

Expect – Writing a Tcl Extension in Only Seven Years (1997)

Related Stories