email@example.com (Will Duquette) writes:
> Here's what Tcl/Tk buys *me*.
> I have no interest in writing large programs solely in Tcl to Tcl/Tk.
> There are indeed better languages out there for that purpose.
> However, in my work we have a developed a number of APIs for a variety
> of obscure tasks. These are generally coded as C libraries. By
> writing Tcl extensions for these libraries, I get the following
> practical advantages:
Currently, I'm developing under a similar paradigm: Write most of the
code in an interactive, interpreted language. Extend with C-code when
interfacing to other libraries, or when doing performance critical
As I see it, this is quite different from "gluing *applications*
together"; instead I extend my interpreter environment to include
C-libraries or other features from the rest of the system that I need.
(Yes, I do have threads as well).
However, I have not used tcl for this, I've been using Python, and
more recently Pike (http://pike.infovav.se). From what I have read and
heard about tcl, I can't see tcl having any advantage over the
languages I have been using (I haven't been doing much
GUI-programming, though). In particular, I find OO-techniques quite