Re: Tclkit 8.5a4 + registry

Uwe Koloska <[email protected]>
Newsgroups gmane.comp.lang.tcl.starkit
Organization voice INTER connect GmbH
Message-ID <[email protected]>
Hello,

Am Mittwoch, 7. Februar 2007 17:45 schrieb Martin Lemburg:
> Hi Larry,
>
> In the "plain" ActiveTcl tclsh the registry command is not present after
> startup.
> In the "plain" ActiveTcl wish the registry command is already present,
> which may depend on tkCon or other startup packages needing the registry
> command.

Can't try this cause I have no globally installed Tcl.  I only use tclkit on 
windows to test -- and develop on linux ;-)

> In the tclkit 8.5a4 and in the tclkitsh 8.5a4 the registry command is also
> not present after startup.

I'm stymied.  To eliminate all possible sideeffects, I have made a simple 
script:
--------------------------------------------------------------------------
set fp [open [file join [file dirname [info script]] testlog.txt] w]
puts $fp "loaded: [info loaded]"
close $fp
exit
--------------------------------------------------------------------------

and drop it onto the former mentioned (and just to be sure freshly downloaded 
from equi4) tclkits, just to get this result:

loaded: {{} Tk} {{} registry} {{} dde} {{} zlib} {{} vfs} {{} rechan} {{} 
Mk4tcl} {{} Itcl}

What magic is going on here???

> But I had recently this "package require ..." error, even with the package
> dde.

I can't require both of this packages:
- registry doesn't provide a version
- and dde provides 1.3.2 instead of 1.3.1

> Currently (right after startup) it is no problem to require the packages
> registry (1.1.5) and dde (1.3.1).

What is the source of your tclkit(s)?
Mine is
  http://www.equi4.com/pub/tk/8.5a4/tclkit-win32.exe.gz
  http://www.equi4.com/pub/tk/8.5a4/tclkit-win32.upx.exe


And there is another thing, that I can't explain.  If a tdom package is in the 
auto_path, it is loaded even without an 'package require'.  And what is 
worse, it's loaded at the first time the auto_path gets scanned for available 
packages (and this means in main.tcl in a standard starkit).

  It's worse, cause on a 64 bit machine a 32 bit starkit provides x86_64 as
  tcl_platform(machine) and so prevents the right 32-packages from loading)

Enough of this mystic things for today
Uwe

-- 
Dipl.-Ing. Uwe Koloska

voice INTER connect GmbH           Tel +351 481 088 3
Ammonstraße 35                     Fax +351 438 399 25
01067 Dresden - Germany            www.voiceinterconnect.de
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.