From: Jeffrey H. <jef...@aj...> - 2000-08-15 21:10:36
|
I'm preparing to make a 1.4 release of TLS. One big change is that TLS will no longer compile against Tcl 8.0-8.1. I've added the following to the README.txt: The TLS 1.4 release requires Tcl 8.2.0+, with 8.3.2+ preferred. The stacked channel implementation in Tcl was originally introduced in 8.2.0 (previously the Trf patch) and rewritten for 8.3.2+ due to inherent limitations in the earlier implementation. TLS 1.4 should compile with any stubs-capable Tcl interpreter, but will require 8.2+ when loaded. There are known limitations in the 8.2.0-8.3.1 stacked channel implementation, so it is encouraged that people use TLS 1.4+ with an 8.3.2+ Tcl interpreter. I've added runtime checking of the channel version (thanks for the code tips Andreas) to allow it to run in any 8.2.0+ Tcl interpreter. I didn't try to support 8.0-8.1 because we know those have the same limitations in the stacked channel implementation. If people are comfortable with using those, then TLS 1.3 has all the same functionality. TLS 1.4 is really meant for use with 8.3.2+, but I added in 8.2.0-8.3.1 because you could make the runtime changes work, and this allows people to compile with 8.2+ and have it work with any 8.2+ interpreter (the test suites will crash if you use a pre-8.3.2 interp though). I've tested the last bits on Solaris and NT with 8.2.0 and 8.3.2. I've dist'ed the current CVS, so you can grab the current sources by checking out the 'tls' module from the head. If there aren't any problems reported soon, I'll be tagging this tls-1-4 and making a release. I was considering making some binary distributions using openssl, but apparently that would have restrictions because we compile a version that has patented stuff that couldn't be redistributed... Oh well, I hear that after Sep. 20th things will loosen up on that front. Jeffrey Hobbs Tcl Ambassador ho...@Aj... Ajuba Solutions (née Scriptics) -- The TclCore mailing list is sponsored by Ajuba Solutions To unsubscribe: email tcl...@aj... with the word UNSUBSCRIBE as the subject. |