Category talk:Tcl: Difference between revisions

(→‎Language features: Revise/refresh reasoning)
 
(3 intermediate revisions by 3 users not shown)
Line 1:
'''Temporary:''' Just so this is easy to find for now. [[Reports:Tasks not implemented in Tcl]]
==Tasks Unlikely to get Implemented==
This is a short discussion of the tasks that are marked with the omit template. —[[User:Dkf|Dkf]] 09:14, 21 May 2009 (UTC)
Line 40 ⟶ 41:
 
We need to check whether these features are enough; if not, we should update the Language template... —[[User:Dkf|Donal Fellows]] 12:26, 1 June 2009 (UTC)
 
=== How to use? ===
What is the correct command to start the examples? I tried 'tclsh' or 'wish', like
$ tclsh <fileWithTheCode>'
but didn't succeed for many of the examples. I use version 8.4 under Debian Squeeze, and I'm aware that all those examples that need a higher version of Tcl won't run. But if I try, for example, the "GUI component interaction" task, I get
invalid command name "ttk::frame"
while executing
"ttk::frame .bg"
If I try "Extend your language", I get
missing close-bracket
while compiling
"set c1 [uplevel 1 [list expr $cond1]
What am I doing wrong? Is 'tclsh' the right command? --[[User:Abu|Abu]] 10:11, 27 August 2010 (UTC)
<hr>
'tclsh' is most often the right command to run the Tcl interpreter. 'wish' is Tcl+Tk (the GUI toolkit), but you can as well add
package require Tk
early in the script, which then can also be called with 'tclsh'.
 
"Extend your language" is buggy (brackets must be balanced) in
set c1 [uplevel 1 [list expr $cond1]
set c2 [uplevel 1 [list expr $cond2]
where a "]" is missing at the end of both lines. I think one should only paste tested code, and test again after editing it...
-- [[User:Suchenwi|Suchenwi]] ([[User talk:Suchenwi|talk]]) 22:34, 30 January 2021 (UTC)
Anonymous user