59

I'm looking for a very straight-forward way of getting the version of the TCL installed on a machine from the command-line. For most programming languages, something along the lines of

languagename -v

provides the information that I want. This does not seem to be an option for tclsh.

The TCL FAQ Q.B21 suggests

echo 'puts $tcl_version;exit 0' | tclsh

but I wonder if there is anything more straight-forward and cross-platform? (I suspect that this would fail mightily on a Microsoft Operating System.)

--

EDIT: Just to emphasize that I'm looking for something that can be executed directly from the operating system command-line. There's all kinds of information available once you start tclsh, but I'm trying to avoid that to ease automated discovery.

  • 6
    If you're also looking for the minor version number, use `puts [info patchlevel]` instead of `puts $tcl_version`. Also, you don't explicitly need to `exit` -- Tcl will see the end of the script and exit on it's own. – glenn jackman Feb 08 '12 at 21:06
  • 1
    Thanks Glenn. That's useful to know. – Simon Peter Chappell Feb 09 '12 at 00:40
  • 1
    Would be interesting to know WHY you need the info. Sometimes in Tcl you don't need the info, because STUBS might make any recent (< 12 years) old Tcl acceptable. – schlenk Feb 10 '12 at 00:17
  • 1
    Perfectly reasonable question. I was wondering about the practicality of automating the recording of the programming language version numbers used by my program (https://bitbucket.org/simonpeter/zadok/) as it uses so many different languages that it could get quite time consuming determining the version numbers manually. I had done pretty well figuring out the other languages, but TCL is new to me and `tclsh` doesn't play like the others do. – Simon Peter Chappell Feb 10 '12 at 02:22
  • `tclsh` CLI API is horrendous! – Ciro Santilli新疆棉花TRUMP BAN BAD Aug 03 '15 at 10:53

3 Answers3

52

This might sound too simplistic, but if you made a script file that contained the commands:

puts $tcl_version

And then ran tclsh sillyscript.tcl, that would execute on all platforms, assuming binary is in PATH. It certainly isn't fancy or flashy, or even neat, but it satisfies that requirement AFAIK.

====

I got curious, so I tried it and without the quotes:

echo puts $tcl_version;exit 0 | tclsh

Executes just fine on my windows box... maybe platform detection prior to the TCL detection is an option?

Niall Byrne
  • 2,388
  • 1
  • 15
  • 17
25

you can do this too.

bash-3.2$ tclsh
% puts $tcl_version
8.6
% info patchlevel
8.6.0

but the best way i think is through echo.

echo 'puts [info patchlevel];exit 0' | tclsh
echo 'puts $tcl_version;exit 0' | tclsh

=======

weird when i tried with out the quotes it didn't work for me. running Mac osx

Darkninja
  • 467
  • 4
  • 10
  • 1
    If you don't put $tcl_version inside single quotes, the bash shell will try and replace $tcl_version with the value from a bash shell variable named tcl_version. Since tcl_version doesn't exist the replacement is a null string, turning "puts $tcl_version" into "puts". Single quotes in the bash shell is like {} in tcl - it stops interpolation. – Scooter Jan 21 '16 at 13:47
  • 1
    Very valuable tip to have added the `info patchlevel` invocation. This makes a difference for example when installing `gcc` since there tcl is "necessary to run the GCC testsuite; see the section on testing for details. Tcl 8.6 has a known regression in RE pattern handling that make parts of the testsuite fail. [...] This bug has been fixed in 8.6.1" Version 8.6 is shipped with Ubuntu 14.04 but the minor release number was hard to get. – XavierStuvw Feb 09 '17 at 09:55
  • Correction on the above. The terminology for the version notation is _major.minor.patchlevel_. So `info patchlevel` gives the version down to the patch level. Incorrect of me to say that the minor release number was hard to get. The patch level was. – XavierStuvw Feb 09 '17 at 19:20
10

Depending on your shell, it could be:

tclsh <<< 'puts [info patchlevel]'