Training, Open Source computer languages
PerlPHPPythonMySQLApache / TomcatTclRubyJavaC and C++LinuxCSS 
Search for:
Home Accessibility Courses Diary The Mouth Forum Resources Site Map About Us Contact
For 2021 - online Python 3 training - see ((here)).

Our plans were to retire in summer 2020 and see the world, but Coronavirus has lead us into a lot of lockdown programming in Python 3 and PHP 7.
We can now offer tailored online training - small groups, real tutors - works really well for groups of 4 to 14 delegates. Anywhere in the world; course language English.

Please ask about private 'maintenance' training for Python 2, Tcl, Perl, PHP, Lua, etc.
run: expect from bash vs. shell-utils from expect

Posted by doublea1535 (doublea1535), 22 August 2006
I am curious about some of the long-term or more in-depth challenges associated with :

1) Running "exec command" commands from within expect. Reasons for this are string manipulation(sed,awk), file manipulation, calling external scripts.


2) Calling expect from within a bash shell. Reasons to do this are : easy option/argument handling via getopts, more comfortable scripting environment; bash regexps/globbing.

Does calling expect from within bash add a serious amount of complexity? Tcl is powerful but I don't need anything that it provides really; at least so far bash and UNIX shell coreutilities seem to be able to do everything I need, and I am much more familiar with them. Is bash able to (quantitatively) process external commands more efficiently than Tcl?

Sorry for the long question. I am really just looking for someone to point me in the right direction of some high-level programming concepts (that I could look further into myself) or a quick blurb.

Thanks much!  

Posted by admin (Graham Ellis), 23 August 2006
Shell programming and core utilities are very powerful indeed for simpler operating system scripting operations, but they become progressively harder to use, and progressively less efficient, as the size of your code / application grows, or when you need portability across operating systems.  

There's no hard and fast rule as to when you should say that a job is too much for shell programming and move across to (say) Tcl, Python or Perl - in other words, there's a big grey area between jobs that are easily done with any of these languages or with shell, and jobs for which it's worth going to all the trouble of learning a new language to support.  Only you can be the best judge os where the crossover point is for you personally.

Posted by doublea1535 (doublea1535), 23 August 2006
Thank you much for the feedback Graham.

This page is a thread posted to the opentalk forum at and archived here for reference. To jump to the archive index please follow this link.

You can Add a comment or ranking to this page

© WELL HOUSE CONSULTANTS LTD., 2022: Well House Manor • 48 Spa Road • Melksham, Wiltshire • United Kingdom • SN12 7NY
PH: 01144 1225 708225 • FAX: 01144 1225 793803 • EMAIL: • WEB: • SKYPE: wellho