Re: Is There Any Reason to Even Use VC++ Anymore?
- From: "Peter Oliphant" <poliphant@xxxxxxxxxxxxxxxx>
- Date: Tue, 6 Dec 2005 09:58:14 -0800
I never did any benchmarks, so I was basing my statement on other reports.
Thus I believe your findings more than what I've read (even though,
ironically, all I've done is read what you've said in saying this...lol). So
speed is not a selling point.
Still, I prefer to use C++ over C#, probably just because I prefer (am more
familiar with) the syntax. And, I'm afraid of seeing this pop up one day on
the MS website:
"MS has deprecated C++ in favor of C#". <shiver>
[==P==]
"Willy Denoyette [MVP]" <willy.denoyette@xxxxxxxxxx> wrote in message
news:%23zRxHf%239FHA.3884@xxxxxxxxxxxxxxxxxxxxxxx
> Sure, for those who believe this nonsense. Those who ran some benchmarks
> know that there is almost no difference, for some specific cases C++/CLI
> is a bit faster and in other cases C# is a bit faster. This is quite
> normal if you know that both front-end compilers emit MSIL and the bulk of
> the optimizations are done at JIT compile time. Sure the C++ compiler can
> spend some extra time to optimize MSIL, while the C# compiler is more time
> constrained, but in reality there is very little that can be done at the
> MSIL level. Note also that a great deal of the code that gets executed in
> a real world application comes from the FCL which is written in C#.
> Believe me, performance is not C++/CLI's selling point.
>
> Willy.
>
> "Peter Oliphant" <poliphant@xxxxxxxxxxxxxxxx> wrote in message
> news:endR7zp9FHA.2676@xxxxxxxxxxxxxxxxxxxxxxx
>> I've heard VS C++.NET can run from 6-10 times FASTER than VS C#.NET.
>> That's a pretty good selling point right there... : )
>>
>> [==P==]
>>
>> "Herby" <prmarjoram@xxxxxxxxx> wrote in message
>> news:1133452860.750447.171420@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>>> We have chosen C++\CLI as our current source code base is in C++ and
>>> provides a clear migration path.
>>> Its also a benefit for us to be able to use mixed mode using both the
>>> un-managed and managed heap in the same application/function.
>>> You could almost think of the syntax extensions almost independent of
>>> .NET. Just can now work with a garbage collector etc.
>>>
>>
>>
>
>
.
- Follow-Ups:
- Re: Is There Any Reason to Even Use VC++ Anymore?
- From: Willy Denoyette [MVP]
- Re: Is There Any Reason to Even Use VC++ Anymore?
- References:
- Re: Is There Any Reason to Even Use VC++ Anymore?
- From: Herby
- Re: Is There Any Reason to Even Use VC++ Anymore?
- From: Peter Oliphant
- Re: Is There Any Reason to Even Use VC++ Anymore?
- From: Willy Denoyette [MVP]
- Re: Is There Any Reason to Even Use VC++ Anymore?
- Prev by Date: Re: I think this is a bug...
- Next by Date: Re: Converting a VS6.0 project to VS2005
- Previous by thread: Re: Is There Any Reason to Even Use VC++ Anymore?
- Next by thread: Re: Is There Any Reason to Even Use VC++ Anymore?
- Index(es):
Relevant Pages
|