Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!goblin3!goblin2!goblin.stu.neva.ru!newsfeed1.swip.net!npeer02.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!spln!extra.newsguy.com!newsp.newsguy.com!news2 From: Michael Wojcik Newsgroups: comp.lang.java.programmer Subject: Re: =?UTF-8?B?QW5kcm9pZOKAlFdoeSBEYWx2aWs/?= Date: Fri, 03 Jun 2011 09:38:54 -0400 Organization: Micro Focus Lines: 35 Message-ID: References: NNTP-Posting-Host: p64865ab05605c997a6fdecbd29b3a647d3146a6c5b3634cb.newsdawg.com Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.5.0 In-Reply-To: Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:4939 Lawrence D'Oliveiro wrote: > > Using MSVC brings its own share of problems. I remember on the Python group, > if you wanted to build a C/C++ extension for Python, you had to compile it > with the exact same version of MSVC as was used for that version of Python, > otherwise it wouldn’t work. There's no "C/C++" language. C and C++ are very different languages.[1] Requiring the same version of MSVC, for a binary compiled from C code, indicates improper use of the C runtime by either Python or the extension. Mixing C runtimes is fine as long as you follow the guidelines Microsoft publishes. In particular, resources allocated by one module shouldn't be freed by another; and some resources (notably FILE* objects) shouldn't be shared between modules. None of this is difficult to achieve. There may be other issues with Microsoft C++, particularly if the versions are very far apart, but on the whole, with properly-designed APIs, there's no reason for this to be a problem. There are certainly many infelicities with MSVC. But most of the problems people have with it are due to sloppy design and coding, and a failure to read and follow the documentation. [1] Yes, I'm well aware that Stroustrop thinks otherwise. I've had that argument (and he participated) on Usenet. I find his argument fundamentally flawed. -- Michael Wojcik Micro Focus Rhetoric & Writing, Michigan State University