All github submissions should be submodules in the assignment repo under your class period. Please see the resources page for help on linking your own repository as a submodule.
You should maintain separate repositories for each assignment.
Submodule naming schema: lastF0f1f2
e.g. dyrland-weaverJon
or konstantinovichSam
or brooksPet
When working with a partner: lastF0f1f2_lastF0f1f2
e.g. brooksPet_dyrland-weaverJon
The first name should always be the earlier name alphabetically
*
Project 02: The Final Frontier
Due: Monday 01/25 10:00am
GitHub Submission Link: git@github.com:mks65/final.git
Work 23: Do Not Put Forks in Sockets
Due: Thursday 01/06 8:00 am
GitHub Submission Link: git@github.com:mks65/23_netfork.git
Work 22: Getting Forks From a Server
Due: Friday 12/17 8:00 am
GitHub Submission Link: git@github.com:mks65/22_fork.git
Work 21: Nevertheless, She Persisted
Due: Wednesday 12/15 8:00 am
GitHub Submission Link: git@github.com:mks65/21_persistent.git
Work 20: Lend Me a Hand
Due: Tuesday 12/14 8:00 am
GitHub Submission Link: git@github.com:mks65/20_handshake.git
Work 19: More Plumbing
Due: Friday 12/10 8:00 am
GitHub Submission Link: git@github.com:mks65/19_names.git
Work 18: Plumbing
Due: Thursday 12/09 8:00 am
GitHub Submission Link: git@github.com:mks65/18_plumbing.git
Work 17: Semaphone!
Due: Tuesday 12/7 8:00 am
GitHub Submission Link: git@github.com:mks65/17_semaphone.git
Project 01: Getting out of your Shell
Due: Tuesday 11/30 8:00 am
GitHub Submission Link: git@github.com:mks65/shell.git
Work 16: Forkin' Around
Due: Wednesday 11/17 8:00 am
GitHub Submission Link: git@github.com:mks65/16_forkin.git
Work 15: Get Argumentative
Due: Monday 11/15 8:00 am
GitHub Submission Link: git@github.com:mks65/15_parse-args.git
Work 14: Light Up the Bat Signal
Due: Wednesday 11/10 8:00 am
GitHub Submission Link: git@github.com:mks65/14_signal.git
Work 13: Instructional Reading
Due: Monday 11/08 8:00 am
GitHub Submission Link: git@github.com:mks65/13_structrw.git
Work 12: Please follow the Dir[ections]
Due: Thursday 11/04 8:00 am
GitHub Submission Link: git@github.com:mks65/12_dirinfo.git
Work 11: /dev[ise a]/random plan
Due: Wednesday 10/27 8:00 am
GitHub Submission Link: git@github.com:mks65/11_randfile.git
Project 00: myTunes
Due: Monday 10/25 8:00 am
GitHub Submission Link: git@github.com:mks65/my_tunez.git
Work 10: Enlist your C skillz
Due: Tuesday 10/19 8:00 am
GitHub Submission Link: git@github.com:mks65/10_list.git
Work 09: Construction Work
Due: Friday 10/15 8:00am
GitHub Submission Link: git@github.com:mks65/09_construction.git
Work 08: If you like it then you should've put a string on it
Due: Friday 10/07 10:00am
GitHub Submission Link: git@github.com:mks65/08_string.git
Work 07: Arrays and Pointers and Functions, oh my!
Due: Tuesday 10/05 10:00am
GitHub Submission Link: git@github.com:mks65/07_funky.git
Work 06: The Old Switcheroo
Due: Monday 10/04 10:00am
GitHub Submission Link: git@github.com:mks65/06_switcheroo.git
Work 05: That way madness lies
Due: Thursday 09/30 10:00am
GitHub Submission Link: git@github.com:mks65/05_pointers.git
Work 04: Make It So
Due: Monday 9/27 10:00am
GitHub Submission Link: git@github.com:mks65/04_make.git
Work 03: Eul Up Your C Engine
Due: Thursday 09/23 10:00am
GitHub Submission Link: git@github.com:mks65/03_euler.git
Task at hand:
Look at the problems here: http://projecteuler.net/index.php?section=problems
They are all math problems of some sort, pick two and write a c program to solve them
Write a function for each problem you solve.
The function should return the solution.
In main
, call each function and print out the results.
Some good starters are problems 1, 5 and 6
Finished early? pick a third, a fourth, a fifth …
Work 02: Git on Up!
Due: Monday 09/22 10:00am
GitHub Submission Link: git@github.com:mks65/01_start.git
Step 0:
Get your GitHub house in order.
Accept the invitation to the mks65 organization (check email, check spam filter)
Set up ssh keys on your home computer and the school computers.
Follow GitHub’s instructions here
Step 1:
Get your home computer setup to compile and run C programs
Write a program where you play around with variables, types and printf.
For extra help, check out the notes .
Use a few different types.
Try out some unsigned
integer types.
Try going out of bounds on either end. This is easiest to work with using char
or short
.
gcc is will let you do things that javac would never condone. You can start to get the feel for that here.
Step 2:
Submit your assignment as a GitHub submodule.
Follow the instructions on the resources page.
Work 01: Compiling your C Knowledge
Due: Friday 09/17 10:00am
Step 0:
Get your home computer setup to compile and run C programs
See notes for potentially helpful C notes.
To work on a Windows computer, it is highly suggested that you install WSL
Follow the instructions to install WSL version 1 and then upgrade to WSL 2.
To work on a Mac computer
Install Xcode from the App Store
Run the following in a terminal in install xcode command line tools: $ xcode-select --install
Example basic C program below:
Work 00: Getting to Know You
Due: Tuesday 09/14 10:00am