Import libraries and Borland C (Was: Wholly unnecessary flame.)

[Martin von Loewis]

"Bruce Dodson" <bruce_dodson.nospam at bigfoot.com> writes:

> This is not true.  

I'm not sure what 'this' you mean; I assume you refer to my statement

> > But then, even *if* Borland C could link with the VC++ compiled
> > python20.dll, you still could not build extension modules with
> > it.

You then wrote

> You can mix and match, as long as you don't export borland-format
> resources to MSVC-based consumers.  That is, if memory is allocated
> by Borland runtime library, it should freed by the Borland runtime.
> If files are opened by Borland stdio, they should be encapsulated
> and not exposed directly to Python.

In Python, you are sometimes required to pass files opened in an
extension to python.dll for consumption, e.g. in PyRun_AnyFile; you
cannot encapsulate them if you want to use that API.

Regards,
Martin