MikkelFJ wrote:
> Sorry for the repost at perl, I didn't release the post was crossposted (I
> entered via Ruby).
> 
> 
> "Neil Madden" <nem00u / cs.nott.ac.uk> wrote in message
> news:LRaA9.1325$J55.292310 / newsfep2-win.server.ntli.net...
> 
> 
>>Hmm.. the more I think about this, the more problems it seems to present.
> 
> I'd
> 
>>love to be able to write an extension, and have it instantly work with x
>>different langauges. Also, I'd love to be able to use Python and Perl
>>extensions from Tcl, without loading seperate interpreters and all that.
> 
> Am I
> 
>>dreaming of an impossible Utopia?
> 
> 
> I wrote some DLL helper logic that makes it easy to query a vtable by name
> in another DLL.
> The vtables can be created in whatever way, but the vtable is not assocated
> with allocated memory, as is the case with COM. This makes it quite flexible
> without really being limited because one could decide that the first
> function should return a 'this' pointer and the second function should be
> the destructor, or whatever.

Basically the same as the Tcl STUBS mechanism for loading extensions in 
different versions of the tcl interpreter without recompiling or 
relinking the extension.

Michael