Is it customary to clean out older conversations? Resolved questions? Trim down a conversation to its conclusion? Would that be impolite? What's teh social norm here?
TCL & Tk, or TCL/Tk?
A question for someone who clearly knows more about TCL than I...Is TCL's graphical combination with Tk normally considered its own language, or is Tk considered a library? If the former, then it makes more sense for GUI TCL snippets to link to Tcl in their section titles, and list Tk as a library. If the latter, then it makes sense for GUI TCL snippets to link to TCL/Tk. --Short Circuit 22:48, 14 February 2007 (EST)
- I fear the answer to all these questions is "yes" ;-) To me, It's always been "TCL/Tk", that is, I rarely use TCL without Tk. On windows, I use Tclkit because it's handy - one single file, can be wrapped up with a couple hundred k of code of whatever I've been writing and a bunch of libraries into a single standalone kit and still fits on a floppy. On Linux I'll sometimes use Tcl alone, i.e. in situations where I might not want or use a GUI, but the GUI aspect is always pretty close. There is, however, such a thing as tclsh (or tclkitsh) which are non-GUI, and people use them that way. And in a sense Tk stands by itself and is even used in other languages (like Perl/Tk or Python/Tkinter). But in those cases it is perceived more of a library while in TCL's case it's really more of an integral aspect of the language itself. It's a gradual thing, I suppose. But strictly speaking [set var value] is Tcl, [puts $var] is Tcl, and [pack [label .l -text $var]] is Tk, even though it follows Tcl syntax. So in my own little world I'd say GUI examples involving Tcl should be "category Tcl/Tk" (which can the redirect to Tcl since it's really the same thing at some level). But I'm entirely open to alternative suggestions. A thread on comp.lang.tcl might be instructive?Sgeier 23:38, 14 February 2007 (EST)
- Does the thread already exist? If not, I can create it. Always good to have linkage back to Rosetta Code, anyway. :-) --Short Circuit 23:34, 18 February 2007 (EST)
Is TCL normally capitalized as an acronym, or is it capitalized as a word (e.g. "Tcl")? --Short Circuit 22:48, 14 February 2007 (EST)
- I have no clue :-) I personally use "TCL" most of the time, but I also use "Tcl". Google gives me 31 million hits on "TCL" and 30.9 million hits on "Tcl" so I guess it's a wash. I guess haggling over spelling isn't "the TCL way". In a wiki, "The TCL way" would be to have pages for "TCL", "Tcl" and "tcl" (and the various combinations with "Tk or "tk") and have them all forward/redirect to the same thing. If TCL is about anything then it is about radical simplicity and "things usually just doing what you expect"... (and is it common to reply to things right here? Or should I reply on your user talk page?)Sgeier 23:38, 14 February 2007 (EST)
- Thanks for the info. Conversations normally take place on the Talk pages where they were started, so this would be a typical example for most conversations. However, user talk pages spawn notifications for the user who owns them. For me, it doesn't matter. I check the "Recent Changes" page and try to examine every page after a change. But as the only wiki sysop and bureaucrat, that's my job. In short, this works for me. YMMV with other users. --Short Circuit 23:33, 18 February 2007 (EST)
- I use “Tcl” because I don't like writing things all in CAPS, but “TCL” is not wrong. (Note that there are other uses of “TCL” out there which can confuse the Google counts, such as a Chinese electrical goods manufacturer; the other form is more exclusive.) —Donal Fellows 20:56, 8 October 2009 (UTC)
- Also, “Tcl” is how the creator of the language referred to it (in books, online writings, etc.)
Would you care to assist me in administrating Rosetta Code? Drop me an email at mikemol (at) gmail.com. --Short Circuit 09:28, 10 May 2007 (EDT)