What's a Checklist?

The programming assignment specifies the general programming assignment. The checklist contains supplemental information, and you are expected to read it prior to submitting your work. Some examples include:

  • Links to any preliminary code. That way, you don't have to retype it yourself.

  • References solutions. Use these to check your work.

  • What to include in your readme.txt file and a template readme.txt file.

  • A link to hints. Novice programmers may find these especially valuable to get started on the assignment.


    • Goals

    Regardless of the operating system that you choose, the goal of Assignment 0 is to make sure that you can:

  • Surf the Web.

  • Write a C program using a text editor specifically designed for writing code, e.g., emacs, lcc-win32, or ProjectBuilder.

  • Compile a C program using an ANSI C compiler, e.g., gcc126 or lcc126.

  • Submit your assignment electronically via the course web page. You won't be able to submit an assignment until you are registered in our system for a precept.
    • Be sure to submit Assignment 0, including the following brief questionnaire. If you don't, the rest of your assignments will not get graded.


    Understanding hello.c

  • Here's a Hello World tutorial that dissects hello.c line-by-line.

  • Bring any remaining "Hello World" questions to the first precept.

  • Some friendly advice from your preceptor: if you're new to C, be sure to read the first few chapters of the King book today. Then read up through Chapter 6 by Monday. If you don't understand something, go to your preceptor for assistance. Don't be bashful or put it off. This is a lot of material to digest, but getting off to a good start in COS 126 will save you lots of energy in the long run.


    • Submission

  • Submit your files via the course home page. Email or hardcopy submissions are not acceptable.

  • The assignment (and submission form) specifies exactly which names to use: hello.c, hello-while.c, hello-if.c and readme.txt. These names are case-sensitive. Do not deviate from these instructions in any way. We process your submissions using an automated script, and you will not receive any credit if you don't follow these instructions. Do not submit executable files - we'll compile them ourselves and run on our system.

  • After you have submitted all of the required files, be sure to hit the Run Script button. You risk losing a substantial number of points if you do not do this and correct any errors.

  • Be sure that every file you submit includes your name, login, and precept number.

  • The readme.txt file must be a text file - MS Word format is unacceptable. Create it using the same editor that you use to write your C code.

  • Be sure that you do the following in your readme.txt file:
  • Write your name, login, and precept number.

  • Write which operating system (e.g., Windows 2000, OS X, Linux) and compiler (e.g., lcc126, gcc126) that you used.

  • Write which editor you used (e.g., wedit, ProjectBuilder, xemacs).

  • List whatever help (if any) that you received.

  • Describe any serious problems you encountered.

  • Do not exceed 80 characters per line. (You may need to put in manual line breaks if your editor does not do this automatically.) The submission system will give you a warning if you exceed the limit.

    • Here is a readme file template to get you started.


    • Enrichment Links

    Here's the ACM Hello World Page. It contains everyone's first program in over 200 programming languages.

    Kevin Wayne