A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2004-January/041679.html below:

[Python-Dev] Re: Switching to VC.NET 2003

[Python-Dev] Re: Switching to VC.NET 2003 [Python-Dev] Re: Switching to VC.NET 2003Paul Moore pf_moore at yahoo.co.uk
Sun Jan 4 17:42:15 EST 2004
"Phillip J. Eby" <pje at telecommunity.com> writes:

>>at the import tables, you do see that runtime symbols are satisfied
>>from msvcrt without the -l flag, and from msvcr71 with it (apart from
>>abort, which is always from msvcrt, which seems to be a peculiarity of
>>how the mingw startup code is linked).
>
> Do you think that's likely to cause any issues?

I can't prove that linking *anything* via msvcrt causes a problem.

And a quick test shows that if user code calls malloc/free/abort, then
those are linked from msvcr71. So it's only if the runtime calls the
function, but your code doesn't, that the msvcrt version is used.
Which is precisely when it doesn't matter (I think).

So no, it won't cause any issues as far as I can see.

Paul.
-- 
This signature intentionally left blank


More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4