By using this site, you agree to our Privacy Policy and our Terms of Use. Close

Forums - General Discussion - How difficult is C++???

twesterm said:
thekitchensink said:
It isn't difficult at all. In fact, I'd say it's incredibly easy. I'm in my first year of my university's Game Development and Entrepreneurship program, and my Programming course is using C# (basically an updated version of C++) and it uses very simple syntax even for the most complex tasks.

It's funny they keep teaching people C# even though most studios don't use it.

And for the record-- I hate Java. I don't know why but I just suck at it.


I'm also quite surprised that they'd teach C# in a games programming oriented course. Then again, I don't really see the point of such specific education programmes. If someone really has a knack for developing games, a typical CS/computer engineering course should give them all (and more) they need to do it.

I'd say that it's also good to be in a more general course, since you never know whether you'll get the career you want or not.

 



My Mario Kart Wii friend code: 2707-1866-0957

Around the Network
NJ5 said:

To be good at C++, you need to should know about OOP - Object Oriented Programming (which is the most used paradigm in C++ programming, although others are possible). A good C++ book should teach you about OOP too.

Fixed.



Words Of Wisdom said:
NJ5 said:

To be good at C++, you need to should know about OOP - Object Oriented Programming (which is the most used paradigm in C++ programming, although others are possible). A good C++ book should teach you about OOP too.

Fixed.


Don't make me laugh.

 



My Mario Kart Wii friend code: 2707-1866-0957

Words Of Wisdom said:
NJ5 said:

To be good at C++, you need to should know about OOP - Object Oriented Programming (which is the most used paradigm in C++ programming, although others are possible). A good C++ book should teach you about OOP too.

Fixed.


 If you don't use OOP you better have some model in mind or all you are going to produce is an unmaintainable mess.



billsalias said:
Words Of Wisdom said:
NJ5 said:

To be good at C++, you need to should know about OOP - Object Oriented Programming (which is the most used paradigm in C++ programming, although others are possible). A good C++ book should teach you about OOP too.

Fixed.


If you don't use OOP you better have some model in mind or all you are going to produce is an unmaintainable mess.


In any case, you wouldn't say someone is good at C++ if they don't even know a lot about OOP. It's just ridiculous.


My Mario Kart Wii friend code: 2707-1866-0957

Around the Network

yeah, agreed. C++ without OOP is not C++. it's a big reason why C became C++.

indeed, on resumes, i've been told to explicitly say OOP next to C/C++ because apparently a lot of people put down C++ when what they really know is just C.



the Wii is an epidemic.

NJ5 said:
twesterm said:
thekitchensink said:
It isn't difficult at all. In fact, I'd say it's incredibly easy. I'm in my first year of my university's Game Development and Entrepreneurship program, and my Programming course is using C# (basically an updated version of C++) and it uses very simple syntax even for the most complex tasks.

It's funny they keep teaching people C# even though most studios don't use it.

And for the record-- I hate Java. I don't know why but I just suck at it.


I'm also quite surprised that they'd teach C# in a games programming oriented course. Then again, I don't really see the point of such specific education programmes. If someone really has a knack for developing games, a typical CS/computer engineering course should give them all (and more) they need to do it.

I'd say that it's also good to be in a more general course, since you never know whether you'll get the career you want or not.

 


 There are some good ones out there that do do(heh, poo) a good job of preparing you though they are few and far between.  Most of these Game Design Degrees teach you what a game is, some good design practices, some basic programming, some basic art, and then send you out the door with no portfolio or experience...to get a tester job...with absolutely no help from the school.

Of course that should probably be expected from places that have professors who teach game design or game programming and have never worked on a game themselves. 



Lingyis said:
yeah, agreed. C++ without OOP is not C++. it's a big reason why C became C++.

indeed, on resumes, i've been told to explicitly say OOP next to C/C++ because apparently a lot of people put down C++ when what they really know is just C.

OOP is a programming paradigm akin to Functional or Procedural.

It is currently the most popular one (much akin to how relational row-based databases are the most popular), however that doesn't make it necessarily the best one for every situation.

Languages as well as techniques/paradigms are simply tools in a good developer's toolbox. Approaching any single tool as the silver bullet solution to all problems will fail.



C++ is easy. C is an assembler mascarading as a high-level language. The former is good for learning descent programming use and syntax. The latter works great for those of us who like to program in 64K of RAM and/or do real-time software.



Words Of Wisdom said:
Lingyis said:
yeah, agreed. C++ without OOP is not C++. it's a big reason why C became C++.

indeed, on resumes, i've been told to explicitly say OOP next to C/C++ because apparently a lot of people put down C++ when what they really know is just C.

OOP is a programming paradigm akin to Functional or Procedural.

It is currently the most popular one (much akin to how relational row-based databases are the most popular), however that doesn't make it necessarily the best one for every situation.

Languages as well as techniques/paradigms are simply tools in a good developer's toolbox. Approaching any single tool as the silver bullet solution to all problems will fail.


 I agree completely that OOP is just another tool. But C++ was designed from the ground up to be used for OOP. Not knowing OOP and claiming to be an expert at C++ is akin to not knowing how to read blueprints and claiming to be a master architect. Both are possible if you use other means to plan your work and communicate it to others, but it would be the exception and not the rule.