Reddit reviews Data Structures and Other Objects Using C++ (4th Edition)

I'm assuming you are looking for generic algo and data struct taught in college:

Look up a university syllabus online, see the name of data structures, learn and implement them in whatever programming language. Same for algorithm, follow some syllebus, learn an algorithm, implement it. For more theory/math pick up a book, follow one of many mooc or find some university course's slides to work with.

I just did a quick search to make sure it is possible to find syllabuses, here's one of them I found for DS: http://bits.usc.edu/cs104/syllabus.html

Here's one for algo: http://www.people.iup.edu/sanwar/COSC%20310%20Syllabus.pdf

For book, my uni used this for DS: https://www.amazon.com/Data-Structures-Other-Objects-Using/dp/0132129485 (good)

For algo: https://www.amazon.com/Introduction-Algorithms-3rd-MIT-Press/dp/0262033844 (overrated, old and confusing, find something better if you can)

ubuntu, cmake, gcc, learn about references, pointers and const correctness, these books: my favorite data structures book, and stupid simple tutorial book

edit: also, I've recently started using Visual Studio Code as an editor. Its pleasant to look at, is multi platform and gets rid of the normal nastiness that you'd normally have to deal with from real visual studio.

While a tad bit pricey, this is a textbook for one of my CSC classes, and you may find it helpful. It isn't an intro book, although it really only take a basic understanding of C++. They explain everything well enough that googling something should resolve any problems.

I recommend this book because it doesn't just show you how to make a program. It shows you how to design a program that is actually useful by using data structures and algorithms. So far, most of my other books have just been "do this, do that" without really having a concrete reason WHY. I'm sure you could find a nice cheap copy somewhere, maybe even an older addition.

Also included is a website that has a lot of code and such that is very useful.

http://www.amazon.com/Data-Structures-Other-Objects-Using/dp/0132129485/ref=dp_ob_title_bk

> Top tip; unless you've got huge linked-list or you've got big objects in the list (or they have expensive copy constructors), it's just as easy (for the programmer) and a lot faster to insert into a vector. In modern C++, you need a really good reason to use a linked list and a really good reason to use a dynamic array.

So... if I'm understanding correctly, the primary reason to use a linked list (insertion being easier) is to improve on the efficiency of a dynamic array, but a vector is more efficient than both, so should supersede them both unless there's a specific need (such as, perhaps, the low available storage of Arduino running on an ATTiny85 or something, in which the overhead of the vector class might pose a problem?) to use an array or linked list?

> Amongst some of the most respected parts of the C++ teaching community, teaching dynamic arrays before vectors is seen as a mistake. An unthinking leftover from thirty years ago when C++ was being learned and taught by C programmers. Now that you've seen it, don't forget it exists, but your standard container should be vector.

This doesn't surprise me. I've been reading that a lot of this exists in the teaching world. It's been a while since my instructors were in industry, but in fairness to them, almost all of the material comes from a couple of books that aren't the most intuitive and, from what I'm hearing, don't necessarily teach in the best way. Gotta love community colleges. ;-)