...C++ is the best portable, objec
oriented and compileable language as of today.
C++ is desirable in many ways, but not all ways. Many programming tasks
do not require maximum performance, but only adequate performance, and
instead do require high productivity for developers.
If you write business apps, writing them in Visual Basic is probably
completely adequate for 98% of them, and that's a lot of applications
and a lot of business in the U.S.A., for example.
One of [God's] influence was my "self"
development (in days when I don't know much about programming and whole
Computer Science). So: some how I decided at first to learn binary nuber
system and then Asembler to know how computers work, next I decided to learn
straight C++ (and C as part of it), then I learn Sql databases. Every of
these I learn in so success full way so I be able to get work as programmer
just after technical high school (in spite of that I was very proly educated
I started in assembly and XBASE, then went to C, later C++ and extended
XBASE languages like Visual FoxPro (an object-oriented version of XBASE).
I've branched out to various other languages over the years, but more or
less my daily development has been C/C++ and VFP, along with some Java.
Now few words abotu ... C#.
How can you tell it is better than C++?
I never said it was better. It's more productive.
It has virtual machine (VM) writen in
C++. True wise programmers write in C++ because it is fast and this is
freedom of life and expressions. So M$ programmers write in C++ and only they
marketings believe that some other programmers are so stupid to adict to M$
specific language, and by desing slow down by VM. The same you can tell about
I write in multiple languages. Even when I wrote Java, I wrote many
functions in C++ using JNI. And I've discovered in C# that there are
delegate functions and marshaling abilities which allow me to transfer
C# types and receive them in C++ DLLs as other types. Visual Studio
even allows me to do native debugging (switching between C# code into
a C++ function, and be able to STEP-INTO that C++ function, or if there
is a delegate callback from C++ into C#, to STEP-INTO that C# function).
It's a very powerful language, mature, and it has strong familiarity
due to its C/C++ derivation.
Another use full wisdom: 80% of language power lies in his libraries. So
don't tell me that some thing is imposible for C++ or easiest in C# - this is
matter of libraries only! Qt shows that C++ is able to be comfortable for
programmer (however they betrayed C++ in flavor they own "mind dissabled"
For business apps, C# has WinForms and a forms designer IDE for rapid form
development. It has a huge host of library support, and a wide range of
examples online in how to code.
In less than a week I took my Visual FreePro, Jr. database engine and
created a class in C# that integrates every function in a way that exposes
that data natively in a way that's easy to use.
It's proven to be a most effective language, and one which interoperates
in every needful way with existing C/C++ code. You can even use pointers
in C# in unsafe code blocks, and native structure types. It allows non-
forward declaration use of all types.
It removes many hurdles seen in C/C++ code in my experience. And the
fact that it runs in a VM means I can write it once and run it on any
machine (save the machine-native DLL support, which would be fairly
easily re-compiled anyway).
More thinking and less stupidity!
I would like to suggest a couple things for you to think about: First,
it's not a good idea to criticize people's faith in God, but only to
bring to the individual's attention those things they do which do not
align with the requirements of God, either in their faith (as being a
hypocrite), or if they believe in something that you don't believe in,
to challenge them to examine their religion and see if it truly pro-
vides what they think it provides.
Second, you seem to think that because I made the decision to leave CLC
and CLC++ as my primary focus in USENET that I am somehow abandoning
C/C++ development, or that I had not given it any thought in making the
I will never leave C/C++. I have hundreds of thousands of lines of code
I've personally written in it. Well-debugged, well-in-use daily code that
I have no intention of re-writing. However, I have a need to move on from
Visual FoxPro. Moving into C# is a natural progression given my skillset,
and it's one I'm happy to pursue.
Rick C. Hodgin