There is truth to your instructor's statement. Nearly all programming languages are composed of keywords that implement datatypes, hardware control, logic, etc. The difference is the words and symbols that are used to implement the logic and the rules that the statements must follow.
Logic is logic is logic is logic, what changes is the logic subset and the keywords. Some languages (such as Java) only implement for and while loops. Others may implement for, do, and while loops (some BASIC dialects, C/C++). Still others may implement something else completely off the wall. Regardless, it is all logic, if a condition is true, a condition is true, if it's false, it's false.
What you need to do is learn to draw parallels between the syntax you already know (VB) and the syntax you don't (C/C++). For example, these are equivalent statements:
dim aNumber as integer = 15
int aNumber = 15;
They both declare and initialize an integer called "aNumber".
Fbody
Posting Maven
2,929 posts since Oct 2009
Reputation Points: 833
Solved Threads: 394
Skill Endorsements: 4
What part of C++ troubles you, my young lad?
firstPerson
Industrious Poster
4,044 posts since Dec 2008
Reputation Points: 851
Solved Threads: 625
Skill Endorsements: 14
It's not as hard as it can be made out to be when i first started anything near coding i learned html then a tiny bit of css and then jumped to c(i really should have learned this one more before jumping to c++ but ..) and then to c++
two invaluable resources i used (its been awhile i don't remember if DW will let me post links or not but not to be rude i will post them as they will help further Op's knowledge of the basics and some advanced concepts)
C tutorials (start with this one first In my opinion it will ease the transition to c++)
C++ tutorials
They are both valuable resources and helped me learn the language pretty quick not as fast as some would like but you can't learn something in a few hours what a couple of months practice takes.
avarionist
Junior Poster in Training
70 posts since May 2010
Reputation Points: 11
Solved Threads: 3
Skill Endorsements: 0
> Why does C++ seem more complicated than Visual Basic?
Because it *is* more complicated than Visual Basic.
But you don't need to be extraordinarily brilliant to learn C++ and to use C++ effectively. Almost all programmers who make a genuine attempt to become good C++ programmers do succeed in their attempts. In a reasonable period of time, which is more than what is required for, say, Visual Basic. The world is complex, some problems are hard, and the tools we use to solve those difficult problems are necessarily more complex.
vijayan121
Posting Virtuoso
1,740 posts since Dec 2006
Reputation Points: 1,236
Solved Threads: 320
Skill Endorsements: 11
I found VB Somehow confusing to me as beginner (Check my first posts), and I moved on with Python and PHP and then C++. I think the only confusing points is when you come to pointers. They are somehow confusing but the other stuffs are somehow simpler.
Many says VB is easy, are referring to GUI drag and drop. But that is even available in C++ using libraries (wxWidgets with Dialog blocks or wxSmith or wxFormbuilder: QT with QTCreator: GTKmm with libglade et al)
So I hope it is not that harder ;)
Stefano Mtangoo
Senior Poster
3,731 posts since Jun 2007
Reputation Points: 462
Solved Threads: 396
Skill Endorsements: 0
When you get a complicated problem, the best tool to start with is a pen and paper (or word processor if you prefer). Write down how you think you would solve the problem, then start translating your thoughts into an algorithm. If it looks feasible, move on to translating to code, if not, back to the drawing board. Many times you will find that it's 2 steps forward and 1 step back when you are working on a project.
Fbody
Posting Maven
2,929 posts since Oct 2009
Reputation Points: 833
Solved Threads: 394
Skill Endorsements: 4
Question Answered as of 2 Years Ago by
thelamb,
Fbody,
vijayan121
and 3 others
When you get a complicated problem, the best tool to start with is a pen and paper (or word processor if you prefer). Write down how you think you would solve the problem, then start translating your thoughts into an algorithm. If it looks feasible, move on to translating to code, if not, back to the drawing board. Many times you will find that it's 2 steps forward and 1 step back when you are working on a project.
UML is helpful, especiall Use case and class diagrams
Stefano Mtangoo
Senior Poster
3,731 posts since Jun 2007
Reputation Points: 462
Solved Threads: 396
Skill Endorsements: 0
Yes, UML is a useful tool, but not everyone knows it. I consider it a mistake to assume that someone does know it. I certainly don't know it, but I'm picking up bits and pieces here and there.
Plus, in my limited experience and for all intents and purposes, it's essentially a pen-and-paper tool that's frequently virtuallized.
Fbody
Posting Maven
2,929 posts since Oct 2009
Reputation Points: 833
Solved Threads: 394
Skill Endorsements: 4