Tcl Source Code

When one uses Stubs to build applications that embed 
Tcl (not extensions), numerous problems are obvious, 
especially on win32.

1) discovering where a Tcl core is is a very difficult 
problem.  Scriptics used HKLM\Software\Scriptics\Tcl in 
their installers, ActiveState uses a different registry key, 
and the makefiles don't set any key.  So when an app 
starts and tries to discover where Tcl is, it gets rather 
complicated and is very fragile.

2) given that you know where a core is located, what 
features does it (they) have?  Does it have symbols and 
memory tracing?  What if I only want a release build with 
memdbg at 8.3.3 only?  What if I can use any core @ 
8.4.1+ but without symbols and don't mind if it has 
threading?  Some info I can derive from the suffix such 
as 't' for threading (but only with makefile.vc as TEA 
doesn't recognize it as a standard suffix), but 'g' isn't as 
meaningful.  'g' could mean only memdbg without 
symbols.

3) As Stubs is the method for runtime linking, it would 
make sense to me that it contain the method for 
connecting to the catalog and loading the core 
requested.

I will add more thoughts to this FR at a later time..

Since TIP #596 is accepted now for Tcl 9.0, this can be closed.

TIP #596 [https://core.tcl-lang.org/tips/doc/trunk/tip/596.md] concept is there now.

More complete implementation in [717ee454f7], not requiring TIP #414 any more
(although TIP #414 would make it more efficient).

First experimental implementation in [ccb77d8416]

Here is an example how this can be done.
[https://www.fossil-scm.org/fossil/info/25f7fa1157]

[http://tip.tcl.tk/414|TIP #414] is a tiny first step
making this easier.

Logged In: YES 
user_id=7549

3.1) IOW, tclstub8x.lib should contain the code to find and 
load a tcl core.