X-FeedAbuse: http://nntpfeed.proxad.net/abuse.pl feeded by 88.191.16.109 Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.dougwise.org!nntpfeed.proxad.net!nospam.fr.eu.org!usenet-fr.net!de-l.enfer-du-nord.net!feeder2.enfer-du-nord.net!feeder1.enfer-du-nord.net!news.glorb.com!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: Tue, 07 Jun 2011 11:48:44 -0400 Organization: Micro Focus Lines: 47 Message-ID: References: NNTP-Posting-Host: p2facfadc7a37c97ea15478ce61cc088bc0375e02dd4fd446.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:5093 Lawrence D'Oliveiro wrote: > 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? Your claim, as stated, describes an attribute of a nonexistent entity. Since the entity does not exist, its attributes demonstrate nothing about the real world. >> 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. No, it is not true of everything built with MSVC. > Are you saying that > MSVC is making “improper use of the C runtime”? A ridiculous argument, even for you. >> 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. Then that's a failure of the Python extension architecture, not of MSVC. There are many things wrong with MSVC, but the particular one you appear to be trying to describe is not one of them. Mixing MSVC runtimes is (unnecessarily) complicated; it is not impossible. -- Michael Wojcik Micro Focus Rhetoric & Writing, Michigan State University