Re: Visual C++ Book
Half question and half comment: If I remember right from my short class all
of the libraries (facilities) of .NET are available to both C# and C++
right? So there is nothing C# can do that C++ can't do. The only thing I
remember really missing is Class Designer, but since I didn't use it much I
don't miss it much yet. Also, the data tips things work better in C#, if I
remember, and you didn't have to type as much to get stuff done. There
seems to be a lot of C# sample code on sites like CodeProject and CodeGuru
and third party libraries are starting to pop up. So, you can't really
argue with success. I think Microsoft's idea of improving C++ for native
makes a lot of sense if it wants to stay in the game with C++. Why not have
C++ be the best (since it's really the only logical) way to write "safe"
native programs?
To
"David Ching" <dc@remove-this.dcsoft.com> wrote in message
news:dcGPh.11061$JZ3.5218@newssvr13.news.prodigy.net...
LOL, I think C# is much more elegant and lacking of complexity (I mean,
just read the code, there is no superfluous junk characters in it to
confuse you, the meaning just leaps out at you), whereas the various C++
community seems to take great delight in seeing how complicated looking
they can make the latest syntax.
OTOH, I am reading Advanced C# by Trey Nash which tells of best practices,
and there is a TON of stuff to learn regarding IDisposable, threading,
exception handling, etc. before one can claim to be proficient in C#. I'm
starting to understand why a lot of expert C# programmers say they wish
WinForms apps weren't so simple, because it makes it easy to do things
wrong.
-- David