From: Harald O. <har...@el...> - 2024-11-11 14:58:47
|
Am 06.11.2024 um 12:58 schrieb apnmbx-public--- via Tcl-Core: > The current mechanism (in the default build config with embedded zip) of > writing a DLL out to disk and loading it has issues on Windows as > described in the TIP. Static linking is proposed as a solution. If this > is not acceptable for whatever reason, at the very least, Jan’s proposal > of not including the DLL’s in the ZIP but instead shipping them > separately is an alternative that should be considered as the current > situation is the least desirable of the three options. > > Personally, I prefer a single binary with all core functionality as that > was the whole purpose behind embedded ZIP’s but I could live with Jan’s > suggestion as well. > > /Ashok Ashok, I am seeing the TIP as critical. I see TIP 703 to solve the time zone/locale request by commands/API as better. The registry package is then only required by 3rd party action. The dde package is anyway a bit outside. If put as fix parts into the core, I would totally vanish the DLL and the requirement of "package require". That would be ok, but for 9.1. The vulnerability by virus checkers to take those dlls as hostile was also my concern. But in the last time, I don't see that any more by any virus checker. I often supposed, that this was an issue with zip-kits, but it never was. The reason often was the direct download of the exe, which then was marked as hostile. An installation routine solved this. I would also love to solve the dll reuse issue in general with the zipkits. Then, the registry/dde does not make any issue any more. Currently, we have 2 external dll's in the standard distribution: libtommath and zip. Adding two additional external dll's in the standard distribution would not make a big difference. Sorry. Thank you for all, Harald |