Re:Tcl the misunderstood (2006)
by helmut_hed on Saturday December 15, 2012 @06:20PM
(#4926664)
Just out of curiosity (having used Tcl shell EDA tools myself) could you Swig stub versions of the proprietary commands and test your scripts standalone?
If you haven't already, you might want to look into Nagelfar. http://nagelfar.berlios.de/
re: TDD -- tcltest ([package require tcltest], man n tcltest) is downright brilliant. Brilliant. It's worth noting that Tcl is the core of the GCC testsuite (dejagnu) as well http://www.gnu.org/software/dejagnu/
Re:Tcl the misunderstood (2006)
by arthurschreiber on Saturday December 15, 2012 @07:55AM
(#4925221)
I also created a very rspec like bdd library, called tclspec: https://github.com/arthurschreiber/tclspec
I find the most unproductive use of my time at work is when writing TCL code. Switching to TDD has helped a lot, but I still find the language maddeningly frustrating.
I hate that this is both valid syntax with wildly different meanings:
I hate that TCL error messages have no prefix, so there is no way to grep for them (the 3rd party tools merge STDOUT and STDERR to a single log).I hate that the TCL error message line numbers are RELATIVE TO THE PROCEDURE instead of relative to the file.
I hate that the language is fully interpreted and not compiled, so you can have a syntax error in a code branch that isn't triggered just lying there for months if you don't fully unit test every code path.
I do not understand how anyone could like TCL unless they were using a linting tool to give the robustness of debugging that most other languages have.
Because of our code base and the 3rd party tools I'm not able to lint our code and it is a brutally painful language to debug.