User Tools

Site Tools


haas:summer2015:data:projects:sll0

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
haas:summer2015:data:projects:sll0 [2015/05/29 14:43] – [list library] wedgehaas:summer2015:data:projects:sll0 [2015/05/31 12:09] (current) wedge
Line 127: Line 127:
     * **list**: list-related unit tests will be here     * **list**: list-related unit tests will be here
     * ...     * ...
-====Operating====+ 
 +=====Operating=====
  
 The project is driven by a fleet of optimized **Makefile**s, which will facilitate the compiling process for us. The project is driven by a fleet of optimized **Makefile**s, which will facilitate the compiling process for us.
Line 212: Line 213:
  
 At this point your code is up to date (obviously the above output will reflect whatever the current revision is). At this point your code is up to date (obviously the above output will reflect whatever the current revision is).
 +
 +====error reporting====
 +To facilitate debugging and correction of errors and warnings in your code at compile time, such compiler messages will be redirected to a text file called **errors** in the base of the project directory.
 +
 +You can view this file to ascertain what errors existed in the last build of the project.
 +
 +With each new project build, this file is overwritten, so you always have the most up-to-date version of compile-time information.
  
 =====Project Overview===== =====Project Overview=====
Line 266: Line 274:
  
 ====List library unit tests==== ====List library unit tests====
-In **testing/list/unit/**, you will find 4 files (along with a **Makefile**):+In **unit/list/**, you will find 4 files (along with a **Makefile**):
  
   * **unit-mklist.c** - unit test for **mklist()** library function   * **unit-mklist.c** - unit test for **mklist()** library function
Line 288: Line 296:
     * ask questions to get clarification!     * ask questions to get clarification!
  
-====Building the code====+=====Building the code=====
 You've made changes to a file in **src/list/**, and are ready to see your results. What do we do? You've made changes to a file in **src/list/**, and are ready to see your results. What do we do?
  
Line 300: Line 308:
 Keep your other terminal in the **~/src/data/sll0/src/list/** directory, so you can more effectively make changes. Keep your other terminal in the **~/src/data/sll0/src/list/** directory, so you can more effectively make changes.
  
-===cleaning things out===+====cleaning things out====
 If you've already ran **make** to build everything a few times, you may want to clean things out and do a fresh compile (never hurts, and might actually fix some problems): If you've already ran **make** to build everything a few times, you may want to clean things out and do a fresh compile (never hurts, and might actually fix some problems):
  
Line 309: Line 317:
 </cli> </cli>
  
-===compile project===+====compile project====
 Next, compile the whole project Next, compile the whole project
  
Line 374: Line 382:
 </cli> </cli>
  
-=====Submission Criteria===== +=====Submission===== 
-To be successful in this project, the following criteria must be met: +{{page>haas:summer2015:common:submitblurb#DATA&noheader&nofooter}}
- +
-  * Project must be submit on time, by the posted deadline. +
-    * Late submissions will lose 25% credit per day, with the submission window closing on the 4th day following the deadline. +
-  * All code must compile cleanly (no warnings or errors) +
-    * all requested functions must be implemented in the related library +
-    * all requested functionality must conform to stated requirements (either on this project page or in comment banner in source code files themselves). +
-  * Executed programs must display in a manner similar to provided output +
-    * output formatted, where applicable, must match that of project requirements +
-  * Processing must be correct based on input given and output requested +
-  * Output, if applicable, must be correct based on values input +
-  * Code must be nicely and consistently indented (you may use the **indent** tool) +
-  * Code must be commented +
-    * Any "to be implemented" comments **MUST** be removed +
-      * these "to be implemented" comments, if still present at evaluation time, will result in points being deducted. +
-    * Sufficient comments explaining the point of provided logic **MUST** be present +
-  * Any and all functions written must have, **at most**, 1 **return** statement +
-    * points will be lost for solutions containing multiple return statements in a function. +
-  * Track/version the source code in a repository +
-  * Submit a copy of your source code to me using the **submit** tool (**make submit** will do this) by the deadline.+
haas/summer2015/data/projects/sll0.1432910626.txt.gz · Last modified: 2015/05/29 14:43 by wedge