Path: csiph.com!x330-a1.tempe.blueboxinc.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!news.linkpendium.com!news.linkpendium.com!newsfeeds.ihug.co.nz!lust.ihug.co.nz!ihug.co.nz!not-for-mail From: Lawrence D'Oliveiro Newsgroups: comp.lang.java.programmer Subject: Re: =?UTF-8?B?QW5kcm9pZOKAlFdoeQ==?= Dalvik? Followup-To: comp.lang.java.programmer Date: Sat, 04 Jun 2011 12:21:03 +1200 Organization: Geek Central Lines: 28 Message-ID: References: NNTP-Posting-Host: 118-92-86-36.dsl.dyn.ihug.co.nz Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8Bit X-Trace: lust.ihug.co.nz 1307146864 14016 118.92.86.36 (4 Jun 2011 00:21:04 GMT) X-Complaints-To: abuse@ihug.co.nz NNTP-Posting-Date: Sat, 4 Jun 2011 00:21:04 +0000 (UTC) User-Agent: KNode/4.4.11 Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:4960 In message , Michael Wojcik wrote: > 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] Relevance being? > 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. But that would be true of everything built with MSVC. Are you saying that MSVC is making “improper use of the C runtime”? > 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 ... Since Python itself provides most of the memory management for objects created by extensions, it’s hard to see how this can be made to work in any practical sense.