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 2023 (and 2024 ...) - we are now fully retired from IT training.
We have made many, many friends over 25 years of teaching about Python, Tcl, Perl, PHP, Lua, Java, C and C++ - and MySQL, Linux and Solaris/SunOS too. Our training notes are now very much out of date, but due to upward compatability most of our examples remain operational and even relevant ad you are welcome to make us if them "as seen" and at your own risk.

Lisa and I (Graham) now live in what was our training centre in Melksham - happy to meet with former delegates here - but do check ahead before coming round. We are far from inactive - rather, enjoying the times that we are retired but still healthy enough in mind and body to be active!

I am also active in many other area and still look after a lot of web sites - you can find an index ((here))
Output to stdout: hidden in Komodo 3.0 ?

Posted by Dimon (Dimon), 6 March 2006
My application combines a several command-line utilities in one large test program system. I calling one part of them with 'exec' command and another part of them is runned  in a separate pipes. But I found that a command-line utility with a long working time don't  show me the output in stdout in real time: the output data is printed into console only after the work of command-line utility is over. I try to flush a buffer, try to configuring an output channel with 'configure' command with -buffering option but all actions were effectless. When the spawned program must to read something from stdin, the user who executed this script don't see an input prompt: it still hidden.

Then, I try to use a simple commmand construction:
Code:
eval exec MPMPrg >@stdout 2>@stderr <@stdin

where MPMPrg is a command line utility name.

Yes! A command line utility start to output it's data into tclsh console. But when I continue to debugging Tcl-script with Komodo 3.0 Pro, I still see nothing and cannot interact with command-line utility   .
Is the anybody Komodo experts with any ideas about this problem?  

And a second question about Komodo: when I debug the script with Komodo, if script requires to input any string data and save it into any variable, the variable not setted! I bound to press a 'pause' button, input the value, press an 'Enter' key and after that set a variable value manually   In tclsh console the same works correctly.
Any ideas to solve this problem?

OS: Win2K Pro SP4.
Tcl interpreter: 8.4.2 with threads support.
Tcl Debugger: Komodo 3.0 Pro.

Posted by admin (Graham Ellis), 9 March 2006
Dimon, you always come up with such excellent (and specific and advanced) questions.   I've left this one uncommented on so far as I don't use Komodo so wouldn't know, and I was just wondering if others might.   You might reach people who know this particular niche if you look at / ask on ActiveState's support services as Komodo's theirs.



This page is a thread posted to the opentalk forum at www.opentalk.org.uk 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., 2024: Well House Manor • 48 Spa Road • Melksham, Wiltshire • United Kingdom • SN12 7NY
PH: 01144 1225 708225 • FAX: 01144 1225 793803 • EMAIL: info@wellho.net • WEB: http://www.wellho.net • SKYPE: wellho