If you want to play with reading/recreating a very small Tcl interpreter, recently I put Picol (a 500 lines of C code Tcl interpreter) on Github. It was still on the web, but a bit more "hidden". I had a chance to re-read the code, and it is not in the category of code I regret writing :D Still relatively useful for newcomers, I hope.
Thanks for that effort. Some time ago, I got Picol working on an Arduino-compatible microcontroller board with minimal effort. I was working towards making my own programmable calculator, and test-drove a number of simple interpreters, including yours and a couple others.
Project languished due to my attention span running out, but I still have my adaptations of those codes on my drive, in case I ever pick it up again.
Thanks for Picol! I saw it as a young engineer, and found the simplicity inspiring. It inspired me to write Tcl interpreters as starter projects in the next languages I was picking up, and I learned a lot by trying to push performance , functionality, and correctness.
Your little project ended up inspiring cumulative months of joyful hacking.
In the 1990s, an awful lot of Linux apps were Tk/Tcl. People complained then about them not being "native", but they were slimmer and better performing than the typical Java or Electron app of today.
MacPorts has far more packages than Homebrew and was implemented by the creator of the original FreeBSD ports system, who was also an employee on Apple’s UNIX team. MacPorts is the standard macOS package manager.
I like Tcl a lot, especially the Expect module. If you've ever wanted an Autohotkey for your terminal (I promise that phrase actually makes sense) it's well worth your time to look into either Expect itself or Python's `pexpect` module.
Package owner: "These configuration choices are so important that a human must be present at the keyboard every time, without exception. Woe would befall us all were the will of the ancients ignored. So it was written, so it shall be done."
This, when I wanted to try tcl, it was so difficult to find ! Somehow I was able to find a tcl executable in my distro.
I challenge anyone to download an executable in less than 2 clics from the page "Binary distribution" of tcl official website [0].
Why is there so much difficulty to provide a binary for TCL ?
[0] : https://www.tcl-lang.com/software/tcltk/bindist.html
Tcl offers a unique combination of embeddability and power, often underappreciated outside specific domains. While its general-purpose usage might be less prominent, its dominance in Electronic Design Automation (EDA) is undeniable.
I use TCL often (forced to) since it's Cloverleaf Integration Engine's official scripting language and it works very well, but it is different from other languages in that its syntax is not modern, though, it's not difficult to learn if you really need to.
It's an older language that's fallen out of favor mostly for other scripting languages (Javascript, Python, etc) and understandably so. I'm by no means an TCL, but do consider myself an expert when using it with Cloverleaf.
What I would recommend right off the bat is installing the handy tool `rlwrap` and starting `tclsh` using the command `rlwrap tclsh`. This wraps it with readline which imo is a better experience (especially if one is used to the readline keyboard shortcuts).
Tcl is more-or-less required if you're involved with the physical design of silicon (most EDA tools only provide a Tcl interface). It's a good fit for that purpose. If you need a language which is easy to embed and you want non-programmers to be able to use it, Tcl is a good choice, though I've heard that Lua has supplanted Tcl for that purpose.
I dropped Perl for TCL decades ago, after I realized that I could read and understand my TCL code months after I’d written it, but my Perl code was totally opaque.
But to be honest, while I feel like Perl has a lot of advantages (full perlre, full access to POSIX APIs, slightly better performance), I still can't look at it and keep my last meal down. Tcl having an event loop and Tk being native are pretty nice too.
I first encountered Tcl when trying to use the network simulator, ns2. Any language that lends itself to such hideous code can't be good, I thought, and stayed clear of it ever since.
So many fond memories of building eggdrop bots with Tcl scripts in the good old days of IRC. Trivia games, quote dbs, channel management, nick squatting, all sorts of shit.
[+] [-] antirez|1 year ago|reply
https://github.com/antirez/picol
[+] [-] analog31|1 year ago|reply
Project languished due to my attention span running out, but I still have my adaptations of those codes on my drive, in case I ever pick it up again.
[+] [-] somekyle2|1 year ago|reply
[+] [-] bulletmarker|1 year ago|reply
[+] [-] watersb|1 year ago|reply
That is to say, its packages are Tcl.
I haven't used it in many years, as is has been largely replaced by Homebrew, which uses Ruby.
(I once maintained a MacOS port of a good-sized scientific analysis package. Hundreds of MacPorts packages, I have debugged.)
https://www.macports.org/
[+] [-] jhbadger|1 year ago|reply
[+] [-] marxisttemp|1 year ago|reply
[+] [-] wglb|1 year ago|reply
[+] [-] IshKebab|1 year ago|reply
https://modules.readthedocs.io/en/stable/modulefile.html
Though there is a replacement that uses Lua which is somewhat better than TCL:
https://lmod.readthedocs.io/en/latest/index.html
TCL is also pretty universally used in EDA scripting. It's pretty bad, though I guess it is better than all the Bash that EDA devs tend to use too.
[+] [-] hiAndrewQuinn|1 year ago|reply
[+] [-] aerostable_slug|1 year ago|reply
Package owner: "These configuration choices are so important that a human must be present at the keyboard every time, without exception. Woe would befall us all were the will of the ancients ignored. So it was written, so it shall be done."
Me: "Yeah, nah."
[+] [-] liveoneggs|1 year ago|reply
[+] [-] unknown|1 year ago|reply
[deleted]
[+] [-] nuancebydefault|1 year ago|reply
[+] [-] WillAdams|1 year ago|reply
https://www.tcl-lang.com/software/tcltk/9.0.html
Any word on a nice binary release of it?
[+] [-] kristopolous|1 year ago|reply
[+] [-] az09mugen|1 year ago|reply
[+] [-] kras143|1 year ago|reply
[+] [-] ChipsNDip|1 year ago|reply
I use TCL often (forced to) since it's Cloverleaf Integration Engine's official scripting language and it works very well, but it is different from other languages in that its syntax is not modern, though, it's not difficult to learn if you really need to.
It's an older language that's fallen out of favor mostly for other scripting languages (Javascript, Python, etc) and understandably so. I'm by no means an TCL, but do consider myself an expert when using it with Cloverleaf.
Thanks!
[+] [-] sureglymop|1 year ago|reply
What I would recommend right off the bat is installing the handy tool `rlwrap` and starting `tclsh` using the command `rlwrap tclsh`. This wraps it with readline which imo is a better experience (especially if one is used to the readline keyboard shortcuts).
[+] [-] zerr|1 year ago|reply
[+] [-] williadc|1 year ago|reply
[+] [-] wduquette|1 year ago|reply
[+] [-] BoingBoomTschak|1 year ago|reply
But to be honest, while I feel like Perl has a lot of advantages (full perlre, full access to POSIX APIs, slightly better performance), I still can't look at it and keep my last meal down. Tcl having an event loop and Tk being native are pretty nice too.
[+] [-] forinti|1 year ago|reply
[+] [-] esafak|1 year ago|reply
https://www.isi.edu/websites/nsnam/ns/
[+] [-] AceJohnny2|1 year ago|reply
That means it's a good language to extend your program. I don't know how it compares to Lua, which seems to have replaced it in that space.
[+] [-] neotek|1 year ago|reply
[+] [-] uwagar|1 year ago|reply
a + b
in Tcl its
expr $a + $b
thats my only beef.
[+] [-] pwg|1 year ago|reply
[+] [-] unknown|1 year ago|reply
[deleted]
[+] [-] hieloz|1 year ago|reply
[+] [-] twothamendment|1 year ago|reply
[+] [-] ksynwa|1 year ago|reply
[+] [-] unknown|1 year ago|reply
[deleted]