Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • Basically what it boils down to is that all the things I've heard people say to try to scare me away from Tcl have turned out to be bogus.

    Are you using extensions, or just core Tcl[/Tk]?

    When I last looked at Tcl (back in the days of 7.6, I think), I was quite turned off that there were so many different extensions, and that some extensions were basically a new environment with Tcl embedded in it (similar to expect). I was less than inclined to start learning/using Tcl when the first task was to sort

    • Well, I think it's safe to say that that's one aspect of Tcl-land that could stand some significant straightening out.

      But letting that daunt one from climbing the Tcl learning curve makes about as much sense as being put off by Perl's alleged shortcomings. I believe that once one has been inculcated with Tcl-think, the range of available extensions may appear as an interesting landscape awaiting exploration. You say that your "first task was to sort out what the differences were between the various OO extensions", but I have to say, I don't believe that's true. Tcl has a core language, and lots of good things can be done with just the core.

      A lot of what there was to dislike about Tcl when you looked at it has been fixed in version 8... but the plethora of extensions isn't one of them. And in this respect, as in so many others, Tcl is close kin to Lisp; and so I, for one, am not inclined to play up the importance of it.

      One of the things I like about Tcl is that it, like Perl, has made no attempt to be paradigmatically pure. (This is the big reason why I'm not at all inclined the invest any time in Ruby or Python.) What Tcl *is*, that Perl isn't, is syntactically simple. It's not quite as simple as Lisp, but almost. As with Lisp (and perhaps this is a weakness), almost all semantics are implemented by "commands" (functions), which can come from anywhere, and so you get very little help from the language itself when you want to figure out what a statement means.