Re: Is There Any Reason to Even Use VC++ Anymore?
- From: "Peter Oliphant" <poliphant@xxxxxxxxxxxxxxxx>
- Date: Tue, 6 Dec 2005 12:12:12 -0800
Here's what I'm getting at. I use to program in C++ before managed stuff
came into play (gc). So, when managed stuff did come into play, I had to
convert my stuff to it. Then CLI came into play. Now I'm converting my stuff
to CLI since gc has been deprecated.
Short of only using 'vanilla' C++, can I ever write code I'm sure will still
be valid 'forever'? That is, code that can be re-used in future projects,
say, 2+ years from now? How can one build a library of tools if the syntax
keeps changing? Hence, I'm even worried about:
"MS has deprecated C++/CLI in favor of C#". <shiver>
Has CLI been made to be 'here to stay", or can we expect some VS.NET 2007
upgrade to possibly deprecate CLI and expect us to learn yet another new
syntax? Like I've mentioned before, one of the purposes of languages like
C++ is the concept it will be re-usable in the future. This constantly
changing the syntax violates that contract.
IMHO, a new version of a product should always be 100% backwards comaptible
IF it's going to be called an UPGRADE. CLI is not backwards comaptible with
'gc', thus requiring conversion time that shouldn't be necessary for an
upgrade, but in this case is absolutely required. Hence, VS 2005 is not an
upgrade to 2003, IMHO, but a 'new' language.
That being said, I really enjoy this new syntax, but wish I hadn't learned
and programmed using "gc" syntax so much. And having done that, I'm worried
a bit about investing time in CLI, since it could be deprecated in a few
years too.
Do we have ANY guarantee along these lines, even in terms of limited-time
(i.e., MS warrants that CLI will NOT be deprecated for X number of years)?
[==P==]
"Willy Denoyette [MVP]" <willy.denoyette@xxxxxxxxxx> wrote in message
news:Os2KVrp%23FHA.3308@xxxxxxxxxxxxxxxxxxxxxxx
>
> "Peter Oliphant" <poliphant@xxxxxxxxxxxxxxxx> wrote in message
> news:ulmaj6o%23FHA.272@xxxxxxxxxxxxxxxxxxxxxxx
>>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>
>>
> C++ != C++/CLI remember!
> What's possible is that you may see "MS has deprecated C++/CLI in favor of
> C#", but they would never deprecate the language (native C++) they use to
> build >95% of their products.
>
>
> Willy.
>
>
.
- Follow-Ups:
- Re: Is There Any Reason to Even Use VC++ Anymore?
- From: Brian Muth
- Re: Is There Any Reason to Even Use VC++ Anymore?
- From: Bo Persson
- 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?
- 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: Is There Any Reason to Even Use VC++ Anymore?
- Next by Date: Re: Is There Any Reason to Even Use VC++ Anymore?
- 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
|
Loading