3 ms·

What was the problem you faced for this solution ?

• 616c 10y ago
  That there was no Tcl implementation for the CLR? Can we not just build cool things? Sorry, I could not help myself. Fun fact: antirez of Redis fame started with an interest in Tcl, and he has written about it. He wrote his own minimalist Tcl implementation in C, despite the original being an exemplary C project (or so I have heard the Tcl codebase is still sometimes used, despite reservation about the resulting language here, as a very clean and easy learning object for teaching language/interpreter design) and I doubt none of his experiences or lessons learned bled into the uber-success that Redis now is, right? http://antirez.com/articoli/tclmisunderstood.html http://antirez.com/articoli/tclmisunderstood.html https://github.com/antirez/jim https://github.com/antirez/jim
  • networked 10y ago
    Though the contents of https://github.com/antirez/jim https://github.com/antirez/jim dates from 2009, Jim Tcl is actively maintained. You'll find the official GitHub mirror at https://github.com/msteveb/jimtcl https://github.com/msteveb/jimtcl. Edit: If this subthread got you interested, antirez's other Tcl projects are worth checking out. They are listed on his page on the Tcler's wiki: https://tcl.wiki/9497 https://tcl.wiki/9497. I particularly recommend https://tcl.wiki/Picol https://tcl.wiki/Picol, the tiny predecessor to Jim Tcl, and https://tcl.wiki/Sugar https://tcl.wiki/Sugar, a macro system for Tcl 8.4+. Disclosure: I maintain a somewhat larger fork of the former.
    • auxym 10y ago
      Jim Tcl sounds really awesome. I use tcl quite a bit as the embedded scripting language in a CAE app. Things like OO with garbage collection and closures/functional primitives are probably what I miss the most from Tcl.
• mistachkin 10y ago
  The original impetus for the project was to create a simple, self-contained Tcl interpreter in managed code.
  • smegel 10y ago
    That's a what, not a why.