At 11/27/2007 04:02 PM, Juan Sanchez wrote:
The reason I suggested Tcl was it makes strings easy. Most everything
is a string in Tcl.
Everything is a string in Tcl :)
I'm not a Tcl noob, and things are not *that* easy in Tcl: when you
have to throw an "eval" now and then, you know someone else is going
to be in trouble understanding that code.
There are also no commas, parenthesis, or quotation
marks. Everyone hates Tcl, and I accept that.
We don't "hate" Tcl at Kitware, we have been using Tcl for a long
long time actually. VTK, our first (and probably largest) OpenSource
product was wrapped pretty early on for that language (before Python
or Java), and it was a satisfying experience; I remember prototyping
VTK projects using Tcl almost 10 years ago, good times. We actually
still rely heavily on Tcl/Tk for "newer" projects like KWWidgets
(http://kwwidgets.org), we are compiling/rolling on own Tcl/Tk
distrib internally every night for more than a few commercial
products, and most of our testing is done in Tcl. See. Bill Hoffman
said it last week: we have plenty of experience with Tcl, and it was
specifically avoided in CMake from the start, probably for that
reason :) This is way too big of a dependency for a build system like CMake.
_______________________________________________
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
