Re: Why does MSDN say this is c++?
- From: "Alex Blekhman" <tkfx.N05P4M@xxxxxxxxx>
- Date: Fri, 3 Feb 2006 22:32:44 +0200
John Carson wrote:
"Tim Roberts" wrote in message
I find the C++/CLI thing very confusing. I thought the
point of Managed C++ was to draw native C++ programmers
gently into the .NET flock, where they would get hooked
by the vastness of the CLR and want to explore C#.
However, C++/CLI is too foreign to draw native C++
programmers in. --
I think if you wander over to
microsoft.public.dotnet.languages.vc
you will find that quite a few native C++ programmers
have been drawn in.
I think it happens because whoever managed to code in C++
professionally has clear understanding that syntax or any
other surface differences just don't matter. A coder who is
proficient in C++ just doesn't need assuasive illusion that
nothing is changed when he goes to explore new technology or
concept. Why to stuck with inappropriate tool when there is
first class one designed from the very beginning with this
technology in mind?
Just look at what happened to JScript.NET or Visual J#. I
think it was mistake to haul these languages into .NET. I
don't know how many people actually do use these languages
for something serious comparing to the similar projects
written outright in C#. Especially JScript.NET puzzles me.
Now it has strong typization, inheritance, classes,
constants, and whatnot. It requires compilation. Is it a
script at all anymore? JScript.NET took worst from both
worlds: unbearable lightness of being script to do any
serious job; castrated semi-OOP features to do any serious
job. All that just for sake of keeping its "scripting" feel
for those who are accustomed to it?
I like to ask my fellow coders when they start new project
in .NET what language they decided to use for it.
Overwhelming majority chooses C#, of course. There is tiny
ammount who decided to use VB or C++ because of harsh time
preasure. Their managers have [naive] idea that coders
already know "the language" (syntax didn't change much,
right?), so why to waste any time, they can start from
tomorrow morning.
.
- References:
- Why does MSDN say this is c++?
- From: Jim Langston
- Re: Why does MSDN say this is c++?
- From: Alex Blekhman
- Re: Why does MSDN say this is c++?
- From: aa
- Re: Why does MSDN say this is c++?
- From: Tim Roberts
- Re: Why does MSDN say this is c++?
- From: John Carson
- Why does MSDN say this is c++?
- Prev by Date: Re: How to control Context Menu
- Next by Date: Static Variables in C++
- Previous by thread: Re: Why does MSDN say this is c++?
- Next by thread: Re: Why does MSDN say this is c++?
- Index(es):
Relevant Pages
|