Note: If a Dean's excuse would authorize an assignment to be submitted more than ten days late or after solutions are released, then the student MAY be asked to complete an equivalent assignment instead.
What | Value | When Due | Spec | Script | Name/Topic |
---|---|---|---|---|---|
Program #1 | 60 | 09/18 (F) | 08/31 | 09/11 | fiend |
Program #2 | 50 | 10/02 (F) | 09/16 | 09/25 | TBA |
Midterm | 10/12 (M) | ||||
Program #3 | 30 | 10/23 (F) | 09/30 | 10/16 | Scripting |
Program #4 | 60 | 11/13 (F) | 10/21 | 11/06 | LZW2020 |
In-class final | 12/02 (W) | ||||
Program #5 | 60 | 12/11 (F) | 11/11 | 11/04 | Shell |
Directory: | /home/classes/cs323/* (handouts; test scripts; other files) | |
Web Page: | http://zoo.cs.yale.edu/classes/cs323 (handouts; links; within yale.edu domain only) | |
Newsgroup: | https://sce.cs.yale.edu/News/cs323/index.html (announcements; responses to e-mail) | |
Mailing List: | http://mailman.cs.yale.edu/mailman/listinfo/cs323 (home delivery of newsgroup) |
However, when the time comes to design the program and write the code, such discussions are no longer appropriate---your solution must be your own personal inspiration (although you may ask members of the teaching staff for help in understanding, designing, writing, and debugging).
Since code reuse is an important part of programming, you may study and/or incorporate published code (e.g., from text books or the Net) in your programs, provided that you give proper attribution in your source code and in your log file and that the bulk of the code submitted is your own. Note: Removing/rewriting comments, renaming functions/variables, or reformatting statements does not convey ownership.
But when you incorporate more than 25 lines of code from a single source, this code (prefaced by a comment identifying the source) must be isolated in a separate file that the rest of your code #include-s or links with. The initial submission of this file should contain only the identifying comment and the original code; revisions may only change types or function/variable names, turn blocks of code into functions, or add comments.
DO NOT UNDER ANY CIRCUMSTANCES COPY SOMEONE ELSE'S CODE OR GIVE A COPY OF YOUR CODE TO SOMEONE ELSE OR OTHERWISE MAKE IT PUBLICLY AVAILABLE---to do so is a clear violation of ethical/academic standards that, when discovered, will be referred to the Executive Committee of Yale College for disciplinary action. Modifying code to conceal copying only compounds the offense.