Tcl Source Code

tclStubsPtr is not exported on win, but is available 
on UNIX.

It has been brought up on c.l.t, that linking a custom 
shell (or application) that includes an extension by 
way Stubs cannot be done due to the extension wanting  
the tclStubsPtr symbol.  Normally, one builds a custom 
shell with implicit linking on win (tcl84.lib), the 
import library.  Mixing tcl84.lib and Stubs 
extensions, albeit quite odd, is not possible due to 
the missing export of tclStubsPtr found in 
tclStubLib.obj.  Stubs libraries are not supposed to 
export their symbols, but if this special case was to 
be allowed, then mixing could be possible.

The patch is minor, but imparts a structure change 
that should be questioned first.

Logged In: YES 
user_id=7549

Too advanced a concept for mortals to comprehend.  Does 
anyone care about such architecture ideas these days?

Logged In: YES 
user_id=7549

If one wants to have version independence with an extension 
within a custom shell (app), I sure would like to know why 
you/one would want to lock themselves to a single version 
of the core :)

Maybe it's best that this feature isn't added, and the UNIX 
side should be considered broken by being public for export.

File Added - 23043: patch.txt