This is why I love Tcl too. As a general purpose language I'd rather use something else, but for projects where you want to make it easy to redefine certain behaviours without rebuilding and you don't want to implement your own DSL (and you shouldn't want that, trust me...) Tcl is right there waiting for you.
I find myself building projects where I implement system specific stuff in C with Tcl bindings and then use Tcl to tie the libraries together. It makes for modular software and easy testing, both unit testing through tcltest and testing stuff interactively in development.
It's not The Best Language(tm), but it really ties the room together.
> It's not The Best Language(tm), but it really ties the room together.
Haha, very well put. A lot of the time, I just want something that lets me tinker interactively with C/++ code (changing variables, calling methods, etc) to make sure it's doing what I want without having to recompile, dive into the debugger, or write a custom command interface. Plus, some things are just far less painful to write in Tcl--namely, anything to do with strings.
I find myself building projects where I implement system specific stuff in C with Tcl bindings and then use Tcl to tie the libraries together. It makes for modular software and easy testing, both unit testing through tcltest and testing stuff interactively in development.
It's not The Best Language(tm), but it really ties the room together.