darwen
April 13th, 2005, 06:03 PM
This is a start of a discussion.
Firstly, I come from a C++/MFC background.
I know C++.NET.
I can't understand why anyone would use it for managed code implementation when other languages like C# are available which are better designed for the job.
In fact the primary purpose of C++.NET is to allow managed and unmanaged code to integrate seemlessly.
However with the interop capabilities of C# why do this ?
Why not keep managed and unmanaged code seperate ?
Debugging doesn't work when jumping between managed and native code in C++.NET. Rendering this process useless.
Besides the fact that intellisense is far worse under C++.NET.
And (I know it's a minor point, but if you're doing it all the time it becomes a major point) the seperator character for namespaces in C# is '.' (i.e. period) and in C++ it is ':' (colon).
I know I've started a heated debate here... let's see what develops.
Darwen.
Firstly, I come from a C++/MFC background.
I know C++.NET.
I can't understand why anyone would use it for managed code implementation when other languages like C# are available which are better designed for the job.
In fact the primary purpose of C++.NET is to allow managed and unmanaged code to integrate seemlessly.
However with the interop capabilities of C# why do this ?
Why not keep managed and unmanaged code seperate ?
Debugging doesn't work when jumping between managed and native code in C++.NET. Rendering this process useless.
Besides the fact that intellisense is far worse under C++.NET.
And (I know it's a minor point, but if you're doing it all the time it becomes a major point) the seperator character for namespaces in C# is '.' (i.e. period) and in C++ it is ':' (colon).
I know I've started a heated debate here... let's see what develops.
Darwen.