3 ms·

I've always been fascinated by TCL, so I second girvo's request. I'd like to know more, with possibly some links to in depth resources, or some insight (as TCL

• saryant 13y ago
  As an example, much of FlightAware is written in Tcl. http://wiki.tcl.tk/15990 http://wiki.tcl.tk/15990
• davidw 13y ago
  Well, it was a pretty vague "manifesto", but Tcl (not TCL) did the event driven thing before it was cool, back in the 90ies. That made it quite responsive for Tk GUI's. Erlang does a lot of the stuff in their manifesto too.
  • memracom 13y ago
    Uhhh... were you aware that basically all the GUI OSes were event driven such as Windows 1.0 and MacOS and AmigaOS etc? Writing desktop applications for any of those OSes involved writing lots of event handlers. And even before that, in the 80s when Lotus 123 reigned in the PC world, that was also built around an event loop. Same with Microsoft's Word 1.0 for MSDOS. TCL did not have anything to do with event loops. Its claim to fame was that it was a simple language with a small footprint that was easy to integrate in any kind of application. Tk was a GUI like all the others, but you were able to write your event handlers in TCL. That doesn't make TCL into an event driven system. It just shows that when you have an event driven system you can factor it into two parts, the event driven core, and the event handlers. Then the event handlers can easily be written in a higher level language to reduce the lines of code and improve productivity.
    • davidw 13y ago
      I didn't say that Tcl was unique in this approach, just that it did it before it was 'cool'. Tcl is very much an event driven system if you want it to be - they're fairly deeply ingrained into how it works.