http://www.cs.nmsu.edu/~jcook/tags/csci2210/ Recent content in csci2210 on Jonathan Cook Hugo -- gohugo.io Thu, 10 Sep 2026 00:00:00 +0000 http://www.cs.nmsu.edu/~jcook/posts/csci2210/ Sat, 15 Aug 2026 00:00:00 +0000 http://www.cs.nmsu.edu/~jcook/posts/csci2210/ Topical (sparse) CSCI 2210 Intro CSCI 2210 Summary C and C++ Index of C/C+ pages Commenting Code Git and GitHub Help Understanding Git and GitHub Creating and Using GitHub Keys Branching and Merging on GitHub (not used) Git Log Pretty Printing (not used) Development Tools Help Unix/Linux Tutorials Unix/Linux Help Unix/Linux Cheatsheet The Make Tool Windows/MacOS Dev Help VSCode Help FLTK on Windows and MacOS External Student Success Is Simple — That Doesn’t Mean It’s Easy Big Six College Experiences Linked to Life Preparedness Welcome to Open Library | Open Library http://www.cs.nmsu.edu/~jcook/posts/c-cpp-index/ Wed, 15 Jan 2025 00:00:00 +0000 http://www.cs.nmsu.edu/~jcook/posts/c-cpp-index/ The most comprehensive C/C++ reference site is CPPReference.com, its main page is C++ but it also has a section on C. Because it is extensive and uses official definitions, it can sometimes be hard to read, but once you get used to it, it is great. (mostly) Plain C Pages (mostly) C++ Pages Introduction to C/C++ Non-OOP C++ Features The C Preprocessor C++ Pointers and References Compiling and Linking OOP Fundamentals Command-line Arguments OOP Inheritance C Input and Output OOP Polymorphism Plain C Strings C++ Strings C Pointers C++ IO Streams Structs and Unions C/C++ Numeric Conversion from Strings Using Const C++ Friend Functions The Make Tool The Gnu Debugger Valgrind Memory Debugger Commenting Code Interesting other resources Yale professor James Aspnes has great notes on C and other topics. http://www.cs.nmsu.edu/~jcook/posts/basic-programming/ Thu, 10 Sep 2026 00:00:00 +0000 http://www.cs.nmsu.edu/~jcook/posts/basic-programming/ 1. ABC, always be compiling Don’t write lots of code and then try to compile and run it. Write small amounts of code, compile and run and test them, and only then write more code. Program in small baby steps always! 2. Be OCD about code indentation (and other style) Do NOT let your code get sloppy, and most especially do not let it be wrongly indented. You will never be able to figure out wrongly indented code by looking at it.