C
Carl Daniel [VC++ MVP]
Ioannis said:
None. I don't think I implied that it did include any.
Rather, C# provides a module concept that works. That concept can only be
simulated through header conventions in native C++.
-cd
None. I don't think I implied that it did include any.
Rather, C# provides a module concept that works. That concept can only be
simulated through header conventions in native C++.
-cd
D
Dan
Olaf said:
In Whidbey it's done with using namespace keywords. e.g. using namespace
System::Windows::Forms;
I
Ioannis Vranos
Carl said:
When you are talking about module concept, do you mean the dlls?
C
Carl Daniel [VC++ MVP]
Ioannis said:
I mean a system with rich meta-data that allows a "client" to be compiled
without needing the source code of the "server". That's the big weakness in
traditional C/C++ - there is no "module" concept that defines a body of
functionality with a clearly defined interface. Instead all we have is a
text-pasting system that can simulate real modules through convention.
In systems that have a cleanly defined module concept (e.g. Borland's
Delphi), changes to the implementation of a module rarely (or
never)necessitate re-compilation of clients of the module. In C and C++,
since all we have to track dependencies is file modification time, there's
simply no way for the compiler to know if a change requires recompilation of
clients or not, so it must take the conservative route and assume that all
changes (to a shared file) are important to clients.
The fact that C++ puts the implementation of the class, even if it's
private, into the field of view of clients further aggravates the situation.
In that regard, I'm not sure that .NET has done enough to shield clients
from internals changes to classes they consume, but it's a big step in the
right direction.
-cd
I
Ioannis Vranos
Carl said:
I do not know much on the subject, but in.NET specifically, one may
create dlls and use them, with no recompilation needed.
C
Carl Daniel [VC++ MVP]
Ioannis said:
Exactly - that's why I say it's a step in the right direction. I'm not sure
it's the complete answer, but it's better than #include.
-cd
W
Willy Denoyette [MVP]
See inline ***.
Ok, but this doesn't prove the claim, it's just the source of all claims. I
was there at teched and when asked about the 25% difference, the answer I
got was - if this was true, the C# compiler team would have done a lousy job
.
Anyway, all benchmarks I have done indicate differences in performance in
between +5% and -5% (yes, sometimes C# is faster).
For real world applications the performance difference is neglectable, don't
forget that the BCL is all written in C#, and the CLR just sits in top of
the same C runtime and Win32.
Don't get me wrong C++/CLI is a great language extension and C++ my language
of choice, but execution speed is not the differentiator when comparing with
other managed languages.
*** Why? What stops the C# compiler to take more time to optimize? Do you
think the C# compiler team is sleeping now?
Willy.
****Ioannis Vranos said:
Ok, but this doesn't prove the claim, it's just the source of all claims. I
was there at teched and when asked about the 25% difference, the answer I
got was - if this was true, the C# compiler team would have done a lousy job
.Anyway, all benchmarks I have done indicate differences in performance in
between +5% and -5% (yes, sometimes C# is faster).
For real world applications the performance difference is neglectable, don't
forget that the BCL is all written in C#, and the CLR just sits in top of
the same C runtime and Win32.
Don't get me wrong C++/CLI is a great language extension and C++ my language
of choice, but execution speed is not the differentiator when comparing with
other managed languages.
*** Why? What stops the C# compiler to take more time to optimize? Do you
think the C# compiler team is sleeping now?
*** The same goes for C# isn't it?
Willy.
O
Olaf Baeyens
Managed C++/CLI producing 25% faster code than C#. Any resources that
difference between managed C++ and C#
I base this experience because I just porter 80% of my managed C++ code to
C# and I do not notice any difference.
This C++ code ported to C# is 'exactly' the same code that I compare with.
The biggest diference is that for managed structures I had to add 'new' for
C# where I did not need this for C++.
I assume in some parts I lose speed and in other parts I gain speed.
The biggest speed gain is in development. The build takes now seconds while
the C++ version takes minutes.
No more fighting with wierd compiler and linker errors, the C# underlines in
red and blue where I have to fix.
Commenting funtions is now actually fun.
Intellisense is lightning fast.
And a far smaller destination dll.
Don't worry, I still use unmanaged C++ for the really preformance critical
functionality.
I don't know how they tested this, but I do not see any visible speed...
****
Ok, but this doesn't prove the claim, it's just the source of all claims. I
was there at teched and when asked about the 25% difference, the answer I
got was - if this was true, the C# compiler team would have done a lousy job
Anyway, all benchmarks I have done indicate differences in performance in
between +5% and -5% (yes, sometimes C# is faster).
For real world applications the performance difference is neglectable, don't
forget that the BCL is all written in C#, and the CLR just sits in top of
the same C runtime and Win32.
Don't get me wrong C++/CLI is a great language extension and C++ my language
of choice, but execution speed is not the differentiator when comparing with
other managed languages.
difference between managed C++ and C#
I base this experience because I just porter 80% of my managed C++ code to
C# and I do not notice any difference.
This C++ code ported to C# is 'exactly' the same code that I compare with.
The biggest diference is that for managed structures I had to add 'new' for
C# where I did not need this for C++.
I assume in some parts I lose speed and in other parts I gain speed.
The biggest speed gain is in development. The build takes now seconds while
the C++ version takes minutes.
No more fighting with wierd compiler and linker errors, the C# underlines in
red and blue where I have to fix.
Commenting funtions is now actually fun.
Intellisense is lightning fast.
And a far smaller destination dll.
Don't worry, I still use unmanaged C++ for the really preformance critical
functionality.
I
Ioannis Vranos
Carl said:
Well each mechanism is different. The #include mechanism is for
compile-time source code inclusion, while the #using mechanism is for
precompiled library use in run time.
I
Ioannis Vranos
Olaf said:I don't know how they tested this, but I do not see any visible speed
difference between managed C++ and C#
I base this experience because I just porter 80% of my managed C++ code to
C# and I do not notice any difference.
This C++ code ported to C# is 'exactly' the same code that I compare with.
The biggest diference is that for managed structures I had to add 'new' for
C# where I did not need this for C++.
I assume in some parts I lose speed and in other parts I gain speed.
The biggest speed gain is in development. The build takes now seconds while
the C++ version takes minutes.
No more fighting with wierd compiler and linker errors, the C# underlines in
red and blue where I have to fix.
Commenting funtions is now actually fun.
Intellisense is lightning fast.
And a far smaller destination dll.
Don't worry, I still use unmanaged C++ for the really preformance critical
functionality.
I guess the major difference will be in C++/CLI and VC++ 2005 and
afterwards.
An interesting article I came across yesterday:
http://blogs.msdn.com/branbray/archive/2003/11/07/51007.aspx