This Repository is contain all my work from Dr.beck's CS180 couse.
Requirement: C++11, clang, g++11
Recommend IDE: CLion
fahrenheit_to_celsius This is lab2, this lab is to compute the Celsius equivalents of two Fahrenheit
circle_calculations This is lab3, this lab is to calculate and display on screen the correct diameter, circumference, and area of a circle
Passer_Rating_Calculation This is lab4, this lab is to calculate the passer rate in American NFL
Java_Joe This is lab5, this lab is to calculate the price of the order
Decisions This is lab6, this lab is to decide the phone plan
More_Phone_Plan This is lab7, this lab is to decide the phone plan with more complicated methods
scores This is lab8, this lab is to get the grade report
game This is lab9, this lab is to play the rock scissors and papaer game
magic_squares This is lab10, this lab is to decide the magic square
searching_sorting This is lab11, this lab is for searching and sorting
dyamic_allocated_array This is lab 12, this lab is for show a Dynamic Array
string This is lab13, this lab is to generate a username for the student’s network and email accounts.
structures This is lab14, this lab helps manage manufacturing inventory
You can access the course using Dr.Beck's website: http://borax.truman.edu/180/
About Dr.Beck: http://borax.truman.edu/
contact me: hl3265@truman.edu
About the Truman State University: https://www.truman.edu/
Following Documents: https://github.com/TheRealMilesLee/Truman-CS180-Documents
This repository is just a collection of my work on the CS180 course, the code is not the perfect, and it may have a lot errors, and some of them were given by the instructor, so the code style may looks so different, and pleas ignore that issue.
Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than right now.
f the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!