Some problems feel like they would be most naturally solved in C++ over C. I don't necessarily mean the ones that cry out for full OO -- but sometimes you really want objects with functions and state -- and that's less natural in C. On the other hand, I wouldn't use C++ for a problem I could solve in C.
Still, given that, I think learning C and C++ at the same time isn't a great idea. I think C++ without OO, templates, STL, etc... is going to be confusingly similar-yet-different to C. My advice would be to focus on your university C course first, since that's what you're meant to be doing at the moment.
Really? I would have thought it'd be easier to go the other way - learn C first. Because you can do everything in C++ that you can do in C, and more. Whereas going the other way I'd expect you to be often confounded by not being able to do something. I suppose C is a lot simpler so maybe it is a good way around to do it.Quote:
Originally Posted by Elkvis
I sort of learned C-like-C++ (it was C++, but I was just learning the C bits of it) first, then C properly, then improved my C++ knowledge somewhat (it's not great). It wasn't a good way to learn -- so OP, if you do decide to learn both, try to keep them separate in your head.