Hi Jeffrey,
>WinCVS should distribute the DLLs if it is built upon it, unless
>if specifically states that it runs on a certain version, which
>people should download. There are difference between versions
>of Tcl, for example 8.1 introduced full unicode and thread-safety
>over 8.0. That makes for a different library. However, all the
>Tcl code works just the same.
I don't think so. The version should be in the version info, the file name
should not change so often - only if previous version is TOTALLY
incompatible. WinCvs is not "build upon" TCL, it rather uses it as an
extension. It works perfectly fine without TCL. But it works better with
TCL. If WinCvs distributes TCL dll's than I can see few problems:
1. If TCL is already installed on given machine you have two versions of the
same dll in the system. Waste the space and make system unstable.
2. Unnecessary increase of the WinCvs installation package size.
3. WinCvs uses the TCL version which differs from the TCL version installed,
while the user things his brand new installation of TCL is the one is used.
BTW: TCL itself is also making that mistake, distributing msvcrt.dll. So I
have 285kB extra on my HDD.
OK, but can you tell me how do I, in my software, find out what version of
the TCL is isntalled? Can you give me some registry key or something like
that, so I can read the filename for the version installed on the given
machine?
BR,
Jerzy
The first thing they don't teach you at school: "Never say never".
All the issues not related to the list please send to me in private, thanks.
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
