Tcl/Tk 8.6.6 RELEASED

[Don Porter]

Tcl/Tk 8.6.6 Release Announcement
July 27, 2016

The Tcl Core Team is pleased to announce the 8.6.6 releases of the Tcl
dynamic language and the Tk toolkit. This is the sixth patch release
of Tcl/Tk 8.6. More details can be found below. We would like to
express our gratitude to all those who submit bug reports and patches.
This information is invaluable in enabling us to identify and eliminate
problems in the core.

Where to get the new releases:
------------------------------

Tcl/Tk 8.6.6 sources are freely available as open source from the
Tcl Developer Xchange web site at:

http://www.tcl.tk/software/tcltk/8.6.html

This web page also contains additional information about the releases,
including new features and notes about installing and compiling the
releases. Sources are always available from the Tcl SourceForge
project's file distribution area:

http://sourceforge.net/projects/tcl/files/

Binaries for most major platforms are available from:

http://www.activestate.com/Tcl

For additional information:
---------------------------

Please visit the Tcl Developer Xchange web site:

http://www.tcl.tk/

This site contains a variety of information about Tcl/Tk in general, the
core Tcl and Tk distributions, Tcl development tools, and much more.

Summary of Changes since Tcl/Tk 8.6.5:
--------------------------------------

This is a patch release, so it primarily includes bug fixes and corrections
to erratic behavior. Highlighted changes are noted below. The changes file
at the root of the source tree contains a more complete list. The Timelines
of all changes are online.

http://core.tcl.tk/tcl/
http://core.tcl.tk/tk/

* [TIP 443] More configuration options for text tags.

* [TIP 446] [$text edit (canundo|canredo)].

* Update to Unicode 9.0.
*** POTENTIAL INCOMPATIBILITY ***

* Final newline in [text] handling restored compat with 8.6.4 and
before.
*** POTENTIAL INCOMPATIBILITY ***

* [file] support for more Windows filesystem conventions.
[5d7ca0,ae61a6]
*** POTENTIAL INCOMPATIBILITY ***

* [namespace upvar $ns] now ignores custom resolvers in $ns.
*** POTENTIAL INCOMPATIBILITY ***

* Tcl_WrongNumArgs() now uses proper list formatting in error message.
Matters when parameter names contain spaces, etc.
*** POTENTIAL INCOMPATIBILITY ***

* Fixed crashes or hangs in...
- [apply {{} {foreach x y {if 1 break else}}}]
- compiled [string replace]
- notifier finalization
- server socket creation on Win
- [glob -path a]
- Tcl_DString appends to self
- mouse pointer warping
- Aqua geometry calculations on new toplevel
- zlib-8.17, zlib-8.18
- apply {{} {lassign {} item; dict update item item item two two {}}}
- [vwait] after namespace delete destroys variable waited on.

* Fix: Safe handling of widget destruction during callbacks.

* Fix: compiled [lreplace $list end ...].
*** POTENTIAL INCOMPATIBILITY ***

* Fix: circumstances of command callbacks from [scale].

* Fix: Stop <Map> event firing from hidden panes of panedwindow.

* Fix: <<Modified>> delivery to text peers.

* Win: Mouse events in exposed window after double click in file dialog.

* Improve support for text bindings customization.

* Improved performance scaling of [namespace delete].

* Xft color font speed.

* Restored support for TclBlend.

* tcltest -relateddir processing in sorted order

* Aqua appearance fixes.

* Updated bundled packages
- tcltest 2.4.0: (TIP 447) execution time verbosity option
- registry 1.3.2:
- Itcl 4.0.5
- Thread 2.8.0
- sqlite 3.13.0

--
Tcl Core Team and Maintainers
Don Porter, Tcl Core Release Manager

--
| Don Porter Applied and Computational Mathematics Division |
| donald...@nist.gov Information Technology Laboratory |
| http://math.nist.gov/~DPorter/ NIST |
|______________________________________________________________________|

[Harald Oehlmann]

Am 27.07.2016 um 20:50 schrieb Don Porter:
> Tcl/Tk 8.6.6 Release Announcement

Congrats and cudos to the Team !
Harald


--- news://freenews.netfront.net/ - complaints: ne...@netfront.net ---

[Dave]

On 7/27/2016 1:50 PM, Don Porter wrote:
> Binaries for most major platforms are available from:
>
> http://www.activestate.com/Tcl

ActiveState's Tcl is 8.6.4 -- no update even for 8.6.5. With this
history I suspect that it will not be updated.

I did a little googling. This is probably not news to many, but
ActiveState was bought by HP recently.

The loss of an easy binary installer for windows (seems to me) will be
to relegate Tcl toward a unix-only platform. I know that I don't have
the time to track down all the source for packages distributed with
ActiveState's Tcl. In addition, man pages are extremely inconvenient on
windows, and I will miss the Tcl help file. I've managed to compile
8.6.5 and replace 8.6.4 in my ActiveState installation, but the packages
remain unchanged.

Are there any hints of a replacement for ActiveState?

--
computerjock AT mail DOT com

[Harald Oehlmann]

On my radar, only the Cloud-Stuff was baught by HP and moved to
San-Francisco including Andreas Kupries, the most active TCL guy at
active state.

It is a fact that all TCL related issues are open now for nearly one
year. They have pushed out the discussable Komodo 10. But I got the
information that this will change and TCL related issues will be addressed.

An easy replacement are the Battery-Included Starkits from René Zaumseil
(kbskit) or Paul Obermeier. It is another style, as anything is included
in one file. I personally enjoy the starkits of Ashok (in twapi) for the
professional level.

ActiveState is definitely a loss. I always hold and pay a licence of the
TCL stuff to motivate them to continue. Maybe also the TCL Association
may contact them. I personally have to admit that I often don't speak
their language.


-Harald

[David Zolli - Kroc]

Thanks a lot for this TCT members!

I updated http://www.zolli.fr/tclkit-darwin.php with 8.6.6 binaries.

[Едуард Зозуля]

In my opinion, AndroWish (www.androwish.org) looks very promising.
The project is young, much has been done, what had not existed at all.
Christian Werner has put a lot of effort in the development of the project.
I think we should all to support this project.

[Dave]

On 7/28/2016 1:17 AM, Harald Oehlmann wrote:
> An easy replacement are the Battery-Included Starkits from René Zaumseil
> (kbskit) or Paul Obermeier. It is another style, as anything is included
> in one file. I personally enjoy the starkits of Ashok (in twapi) for the
> professional level.

I don't understand how a "kit" can be a substitute for a complete Tcl
installation.

Please correct me if I'm wrong, but is not a "kit" just a means to wrap
a Tcl application into a single executable?

If so, then
1) how would I link an package I compile against the stub library?
2) how would I develop a new script from scratch?
3) how (on windows) would I double-click on a script and have it execute?
3) how would I install or update an package (even a non-binary one)?

The windows help file for Tcl does not come in a kit either, right? Nor
the help for all the packages.

And even if I compile Tcl from source, I'm still missing essential
packages like (in my case) Img. Furthermore, is not the source for all
the Tcl packages included in the ActiveState installation scattered all
over the internet? It would be very difficult for someone to track down
and get them compiled correctly.

This is far beyond the ability of a typical windows user who,
previously, could simply run the ActiveState installer (which most
windows users know how to do) and be done.

(I don't mean to rant but I'm looking for an equivalent replacement for
the ActiveState installers for Tcl on windows.)

[David Zolli - Kroc]

Le jeudi 28 juillet 2016 17:37:03 UTC+2, Dave a écrit :
> I don't understand how a "kit" can be a substitute for a complete Tcl
> installation.

A starkit can't: that's (partly) the job of the tclkit/basekit runtime.

You should have a look at http://wiki.tcl.tk/3661 to understand ow it works.

> ../..

> 1) how would I link an package I compile against the stub library?

I think you can't. You need Tcl sources to build extensions.

> 2) how would I develop a new script from scratch?

Exactly the same way you would do it with standard Tcl/Tk distribution.

> 3) how (on windows) would I double-click on a script and have it execute?

I'm definitly not a Windows expert, but I think you can associate .tcl extension with a tclkit runtime.

> 4) how would I install or update an package (even a non-binary one)?
The answer depends if you mean on your own computer or if you want to package it for an script you want to share.

> The windows help file for Tcl does not come in a kit either, right?

Nope, you'll have to bookmark and use http://www.tcl.tk/man/tcl8.6/ like Mac and unix tclers. ;)

> And even if I compile Tcl from source, I'm still missing essential
> packages like (in my case) Img. Furthermore, is not the source for all
> the Tcl packages included in the ActiveState installation scattered all
> over the internet? It would be very difficult for someone to track down
> and get them compiled correctly.
>
> This is far beyond the ability of a typical windows user who,
> previously, could simply run the ActiveState installer (which most
> windows users know how to do) and be done.

That's the reason why:

A) I try to use pure tcl packages only: they are way easier to keep up to date.

B) When I hate to use a binary extension, I only choose a very popular one, with a known website where I can get reliable binaries

C) I use http://wiki.tcl.tk a lot.

[pal...@yahoo.com]

On Thursday, July 28, 2016 at 9:07:03 PM UTC+5:30, Dave wrote:
> (I don't mean to rant but I'm looking for an equivalent replacement for
> the ActiveState installers for Tcl on windows.)
>
> --
> computerjock AT mail DOT com

Sadly, I don't think there is one. In particular, one with the "teapot" functionality. I think there might be some efforts under way in this regard but it will probably take time. One can only hope ActiveState returns in due course.

I'm toying with a Windows installer myself for a "batteries included" distribution but even if it comes to fruition, it certainly will not have the package update over the internet feature.

/Ashok

[Dave]

On 7/28/2016 11:15 AM, pal...@yahoo.com wrote:
> Sadly, I don't think there is one. In particular, one with the "teapot" functionality. I think there might be some efforts under way in this regard but it will probably take time. One can only hope ActiveState returns in due course.

That would be too bad. I would bet that without a simple windows
installer, Tcl will become a unix-only language where the only presence
on windows would be a unix app which a unix developer chooses to port to
windows as one of these kits.

[Brad Lanam]

I don't think we need the package update over the internet initially. That can be added later. As long as there is a way to download a package from a website and the run some sort of add-package-to-tcl-distribution script.

Let me know if you want help with testing, building or whatever. I have Windows XP, 7-32, 7-64, 8.1-32, 8.1-64 and 10 available (and Win2K also, but that's a bit old).

Dave wrote:
> And even if I compile Tcl from source, I'm still missing essential
> packages like (in my case) Img.

The Img package downloads at sourceforge have pre-compiled shared libraries
and all work well with a tclkit or with the compiled sources.
I didn't package them inside the tclkit,
just in a folder outside and added it to the autopath.

I was not able to get tdom working within a 32-bit tclkit, so I am definitely
interested in helping to get a new Windows distribution up and running.

[Christian Gollwitzer]

Am 28.07.16 um 17:36 schrieb Dave:

> On 7/28/2016 1:17 AM, Harald Oehlmann wrote:
>> An easy replacement are the Battery-Included Starkits from René Zaumseil
>> (kbskit) or Paul Obermeier. It is another style, as anything is included
>> in one file. I personally enjoy the starkits of Ashok (in twapi) for the
>> professional level.
>
> I don't understand how a "kit" can be a substitute for a complete Tcl
> installation.

I'm using only tclkits as my primary Tcl distribution for years now (on
Linux and OSX, but it also works on Windows).

> Please correct me if I'm wrong, but is not a "kit" just a means to wrap
> a Tcl application into a single executable?
>
> If so, then
> 1) how would I link an package I compile against the stub library?

You need to have the stub library as an external file; if you compile
the kit by yourself (or only Tcl & Tk), you will have the stub library.
It is then compatible with the kit.

> 2) how would I develop a new script from scratch?

You write it in a text editor, as usual. A tclkit is nothing but a Tcl
interpreter containing all dependent files. So you run your program like

tclkit-whater.exe myscript.tcl

from the command prompt.

> 3) how (on windows) would I double-click on a script and have it execute?

You associate the .tcl file extension with the tclkit.exe file. Haven't
done this on very recent Windows (10...), but on Win 7 you can just
right-click "Open with..." on the .tcl file and then select that it
should alway open with the tlckit.exe

> 3) how would I install or update an package (even a non-binary one)?

You can't easily install a package into the kit. It is possible, in
theory, by decomposing the kit using "sdx" and reassembling. But that is
not really necessary. I usually append to the top of my scripts
something like

lappend auto_path [file join [file dirname [info script]] lib]

and then you just put your packages in a folder called lib where the
script resides. Same way you could make a lib directory at the place of
the tclkit, for instance by doing

lappend auto_path [file join [file dirname [info nameofexecutable]] lib]

> The windows help file for Tcl does not come in a kit either, right? Nor
> the help for all the packages.

Yes. That is the only really missing point, ActiveTcl has made nice html
documentation. For tcllib, I think it can be generated from the
Makefile, not sure about the rest. Typically I use Google these days to
find the docs.

> And even if I compile Tcl from source, I'm still missing essential
> packages like (in my case) Img.

Larger distros like kbskit come with Img and a large set of packages.
See here: https://sourceforge.net/projects/kbskit/files/kbs/0.4.8/
Unfortunately, TLS is not included in Windows, because it doesn't
compile out of the box. On OSX and Linux it does, though.

> Furthermore, is not the source for all
> the Tcl packages included in the ActiveState installation scattered all
> over the internet? It would be very difficult for someone to track down
> and get them compiled correctly.

Yes and no. kbs.tcl has paths for all of the software included in its
packagefiles. It downloads and builds the software automatically.

> This is far beyond the ability of a typical windows user who,
> previously, could simply run the ActiveState installer (which most
> windows users know how to do) and be done.

The equiv is to download the kbskit...-bi.exe und run it. It's not an
installer, but an "installer" really would only copy it to C:\Program
Files or similar. Maybe the file association and a start menu link.

Christian

[Rich]

Dave <nor...@nohost.com> wrote:
> On 7/28/2016 1:17 AM, Harald Oehlmann wrote:
>> An easy replacement are the Battery-Included Starkits from René Zaumseil
>> (kbskit) or Paul Obermeier. It is another style, as anything is included
>> in one file. I personally enjoy the starkits of Ashok (in twapi) for the
>> professional level.
>
> I don't understand how a "kit" can be a substitute for a complete Tcl
> installation.

Not a substutite for a complete, including C headers, Tcl install, but
a kit exe can substitute for _most_ of the reasons one would have
installed ActiveState's Tcl distribution.

> Please correct me if I'm wrong, but is not a "kit" just a means to
> wrap a Tcl application into a single executable?

That's not the only use - but that is the major use and the one most
advertised, so it is easy to think that is all they can do.

> If so, then
> 1) how would I link an package I compile against the stub library?

A kit is not a substitute for this one. After linking, it can be a
substitute for the runtime installed by the installation package.

> 2) how would I develop a new script from scratch?

Notepad, wordpad, notepad++, etc. (i.e., your text editor of choice).
This one is unrelated to the kind of installation.

> 3) how (on windows) would I double-click on a script and have it
> execute?

Tell windows to associate *.tcl files to the kit executable file, then
double clicking them launches them just like any other program. I
launch Tcl scripts this way on my work computer all the time.

> 3) how would I install or update an package (even a non-binary one)?

Pick a "lib" directory location on your C: drive. Put your packages
there. As one of the first stanza's of your scripts, add that
directory to the auto_path global (and/or to the module path if you use
'modules').

Update is then as simple as replacing the existing files in that "lib"
dir with the new replacement updated files.

> The windows help file for Tcl does not come in a kit either, right? Nor
> the help for all the packages.

You do lose this, so this is one of those spots where a kit is not a
"full" replacement.

> And even if I compile Tcl from source, I'm still missing essential
> packages like (in my case) Img. Furthermore, is not the source for all
> the Tcl packages included in the ActiveState installation scattered all
> over the internet? It would be very difficult for someone to track down
> and get them compiled correctly.

This one is true, although the "batteries included" kits often already
have popular packages such as Img already installed inside the kit, so
you would not need to track those down yourself.

> This is far beyond the ability of a typical windows user who,
> previously, could simply run the ActiveState installer (which most
> windows users know how to do) and be done.

A typical windows user is also not going to be compiling against the
stub library, developing new scripts from scratch, nor installing
libraries (binary or pure tcl). For the "typical windows" user you'd
be better off using the "make a single blob" mode of Tclkit to hand
them a single file executable they can double click. Then they only
have to understand "double click this thing".

> (I don't mean to rant but I'm looking for an equivalent replacement for
> the ActiveState installers for Tcl on windows.)

If you want everything AS provided, then there is no equivalent. Kit's
can support many of the use cases for which an advanced user would have
wanted to install the AS bundle, but not all of those use cases.

[Óscar Fuentes]

pal...@yahoo.com writes:

> Sadly, I don't think there is one. In particular, one with the
> "teapot" functionality. I think there might be some efforts under way
> in this regard but it will probably take time. One can only hope
> ActiveState returns in due course.
>
> I'm toying with a Windows installer myself for a "batteries included"
> distribution but even if it comes to fruition, it certainly will not
> have the package update over the internet feature.

The MSYS2 project [1] contains Tcl/Tk along with several popular
packages. Contributing new packages is easy. You can install/update from
the Internet with `pacman -S package-name' [2]. New versions are
published a few days after the upstream release [3]. It has both 32 and
64 bits packages. It is not difficult to extract the packages you are
interested on for creating your own binary distribution (something that
ActiveState does not allow.)

1: https://msys2.github.io/

2: For instance:
pacman -S mingw-w64-i686-tktable

3: If it takes too long, you can update the version number and request a
rebuild through a Github pull request.

[Harald Oehlmann]

Am 28.07.2016 um 21:18 schrieb Christian Gollwitzer:
> Am 28.07.16 um 17:36 schrieb Dave:

>> The windows help file for Tcl does not come in a kit either, right? Nor
>> the help for all the packages.
>
> Yes. That is the only really missing point, ActiveTcl has made nice html
> documentation. For tcllib, I think it can be generated from the
> Makefile, not sure about the rest. Typically I use Google these days to
> find the docs.

Ashok has a great help file in window hlp format. It is always on my
desktop:
https://sourceforge.net/projects/twapi/files/Combined%20Help%20Files/

[Harald Oehlmann]

Am 28.07.2016 um 18:15 schrieb pal...@yahoo.com:
> I'm toying with a Windows installer myself for a "batteries included" distribution but even if it comes to fruition, it certainly will not have the package update over the internet feature.

Great news, Ashok!
If you could do a 8.6.6 starkit with twapi, this would also continue to
be on my favorites !

Thank you for your continuous great work,

[Harald Oehlmann]

Am 28.07.2016 um 23:46 schrieb Óscar Fuentes:
> It is not difficult to extract the packages you are
> interested on for creating your own binary distribution (something that
> ActiveState does not allow.)

Unfortunately, this kis not true. Each Active-State packages is
available via aWEB site without Teapot. Of cause, Teapot is ok too.

Nevertheless folks. Please try to pass money to Activestate. That might
be the only motivation for them to continue. It is a company ;-)

And to edit TCL, Komodo is really great.

[Óscar Fuentes]

Harald Oehlmann <wort...@yahoo.de> writes:

> Am 28.07.2016 um 23:46 schrieb Óscar Fuentes:
>> It is not difficult to extract the packages you are
>> interested on for creating your own binary distribution (something that
>> ActiveState does not allow.)
>
> Unfortunately, this kis not true.

What is not true?

> Each Active-State packages is
> available via aWEB site without Teapot. Of cause, Teapot is ok too.

The fact that the ActiveState package is available on the web does not
mean that you can legally use the package on your own terms. Read their
License, specifically the part that talks about redistribution.

[snip]

[Harald Oehlmann]

Am 29.07.2016 um 15:15 schrieb Óscar Fuentes:
> Harald Oehlmann <wort...@yahoo.de> writes:
>
>> Am 28.07.2016 um 23:46 schrieb Óscar Fuentes:
>>> It is not difficult to extract the packages you are
>>> interested on for creating your own binary distribution (something that
>>> ActiveState does not allow.)
>>
>> Unfortunately, this kis not true.
>
> What is not true?

You can grab them easily but the licence issue is true.

>> Each Active-State packages is
>> available via aWEB site without Teapot. Of cause, Teapot is ok too.
>
> The fact that the ActiveState package is available on the web does not
> mean that you can legally use the package on your own terms. Read their
> License, specifically the part that talks about redistribution.

That is true.

Thank you,

[mse...@gmail.com]

On Thursday, 28 July 2016 09:06:49 UTC+2, David Zolli - Kroc wrote:
> Thanks a lot for this TCT members!
>
> I updated http://www.zolli.fr/tclkit-darwin.php with 8.6.6 binaries.

David I have tried to download your starkits, and after unzed/unzip them I just have a file tclit.8.6.6, If I double click MacOS asks for an application, I tried adding the extension .app but cannot get the kit to run is there something else to do ?

Martyn

[Christian Gollwitzer]

Am 16.08.16 um 14:55 schrieb mse...@gmail.com:

I think double-clicking is not working on OSX, unless you create an
actual .app-structure (it's a special directory structure + some XML
file). Go to a terminal, cd to where the file is and try:

chmod +x tclkit8.6.6
./tclkit8.6.6

Christian

[mse...@gmail.com]

On Tuesday, 16 August 2016 16:00:02 UTC+2, Christian Gollwitzer wrote:
> Am 16.08.16 um 14:55 schrieb ms...@gmail.com:

Your right it is a terminal app. If I execute it on the terminal command line it works, and I can package require Tk to open the toplevel window.
As you say there is no way to get it running from the finder.

Now I have to do some SDX work and try a few other things.

Martyn

[Christian Gollwitzer]

Am 16.08.16 um 16:27 schrieb mse...@gmail.com:

If you want to see, how I do it, checkout http://auriocus.de/OSXAppDemo/
it contains a demo/Makefile for a script which is wrapped as a
Mac-application including creating the dmg. You'll only have to replace
the runtime file with the new tclkit.

Christian

[David Zolli - Kroc]

Le mardi 16 août 2016 14:55:37 UTC+2, mse...@gmail.com a écrit :

> David I have tried to download your starkits, and after unzed/unzip them I just have a file tclit.8.6.6, If I double click MacOS asks for an application, I tried adding the extension .app but cannot get the kit to run is there something else to do ?

Hi Martyn,

Yes, it's a terminal app.

If you want to try a graphical app, you can download http://www.zolli.fr/fichiers/tkcon.zip (but it includes tclkit 8.6.4, not the last version).

BTW, it's pretty simple to update it. ;)

[carmo...@gmail.com]

Certainly, choosing an AndroWish distro as the official TCL distro for all platforms would be a great idea. Besides, TCL is going to experience a second youth with the internet of things, and the small language of things, namely TCL.

[Едуард Зозуля]

среда, 17 августа 2016 г., 17:53:26 UTC+3 пользователь carmo...@gmail.com написал:

ESP8266 + jim - it would be great

[Andreas Kupries]

Harald Oehlmann <wort...@yahoo.de> writes:

> Am 28.07.2016 um 00:18 schrieb Dave:
>> On 7/27/2016 1:50 PM, Don Porter wrote:
>>> Binaries for most major platforms are available from:
>>>
>>> http://www.activestate.com/Tcl
>>
>> ActiveState's Tcl is 8.6.4 -- no update even for 8.6.5. With this
>> history I suspect that it will not be updated.
>>
>> I did a little googling. This is probably not news to many, but
>> ActiveState was bought by HP recently.

>> Are there any hints of a replacement for ActiveState?
>
> On my radar, only the Cloud-Stuff was baught by HP and moved to
> San-Francisco including Andreas Kupries, the most active TCL guy at
> active state.

More clarifications:

HP only bought the stackato Assets, i.e. Cloud Stuff, PaaS.

The office did not move.

I am still sitting in the same physical office in Vancouver as before.
ActiveState moved out to a new location (a few blocks west down the
same street (Hastings)).

--
So long,
Andreas Kupries <akup...@shaw.ca>
<http://core.tcl.tk/akupries/>
Developer @ Hewlett Packard Enterprise

Tcl'2016, Nov 14-18, Houston, TX, USA. http://www.tcl.tk/community/tcl2016/
-------------------------------------------------------------------------------

[Harald Oehlmann]

Am 09.09.2016 um 06:12 schrieb Andreas Kupries:

> Harald Oehlmann <wort...@yahoo.de> writes:
>> On my radar, only the Cloud-Stuff was baught by HP and moved to
>> San-Francisco including Andreas Kupries, the most active TCL guy at
>> active state.
>
> More clarifications:
>
> HP only bought the stackato Assets, i.e. Cloud Stuff, PaaS.
>
> The office did not move.
>
> I am still sitting in the same physical office in Vancouver as before.
> ActiveState moved out to a new location (a few blocks west down the
> same street (Hastings)).

Dear Andreas,

thank you for the message. Great to hear from you.
I appreciate all your action, most visible with TCLLIB.

So I can still physically redirect the ActiveState people to you in case
of issues... ;-)

Thanks,