[cfe-dev] libc++ in Windows

[Óscar Fuentes]

[fixed top-posting]

James Gregurich <bayoubengal at mac.com> writes:

> On Jun 30, 2013, at 9:18 PM, Nico Rieck <nico.rieck at gmail.com> wrote:
>
>> Due to how shared libraries work on Windows, this isn't a problem
>> (as long as you're careful with resources). And Microsoft's APIs use
>> only C (or more specifically a subset) and COM.
>
> How about libs like MSHMTL and JSCRIPT? 

MSHTML has a COM interface. And I wouldn't consider it a core library by
any stretch. Dunno about JSCRIPT but I'll bet that it is the same case.
For core (OS) functionality, it is in the best interest of MS to not
block access to other compiler vendors. Also, historically MS promoted
other languages over C++ and that means that its libraries hide its C++
implementation behind a COM/C interface.

To recap: there is no problem using C++ runtimes other than MS on
Windows. MinGW does it, Borland does it...