Re: ELKS and .NET
> The ability to link modules from different languages is notIt's largely true, but there has been some instances of mixed
> new (...), and was never widely adopted.
languages in widespread use: on Unix, scripting languages associated
with C libraries (python etc), and with Windows UIs with VB as glue
for C/C++ UI components.
> I do not believe it makes our work here obsolete or redundant.Agreed.
> Furthermore we are not only specifying basic classes here. We areWe're constrained by the existing though, although there's
> also setting an example on how it should be done.
still scope for doing good things within that constraint.