User Tools

Site Tools


haas:fall2016:common:submitblurb

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:fall2016:common:submitblurb [2017/08/27 20:43] wedgehaas:fall2016:common:submitblurb [2021/09/08 17:12] (current) wedge
Line 15: Line 15:
     * Early submissions will earn 1 bonus point per full day in advance of the deadline.     * Early submissions will earn 1 bonus point per full day in advance of the deadline.
       * Bonus eligibility requires an honest attempt at performing the project (no blank efforts accepted)       * Bonus eligibility requires an honest attempt at performing the project (no blank efforts accepted)
-    * Late submissions will lose 25% credit per day, with the submission window closing on the 4th day following the deadline. +    * Late submissions will lose 33% credit per day, with the submission window closing on the 3rd day following the deadline. 
-      * To clarify: if a project is due on Wednesday (before its end), it would then be 25% off on Thursday, 50% off on Friday, 75% off on Saturday, and worth 0% once it becomes Sunday.+      * To clarify: if a project is due on Wednesday (before its end), it would then be 33% off on Thursday, 66% off on Friday, and worth 0% once it becomes Saturday.
       * Certain projects may not have a late grace period, and the due date is the absolute end of things.       * Certain projects may not have a late grace period, and the due date is the absolute end of things.
   * all requested functions must be implemented in the related library   * all requested functions must be implemented in the related library
Line 65: Line 65:
       * 1/3: Minimal error checking, code is fragile (code may not work in full accordance with project requirements)       * 1/3: Minimal error checking, code is fragile (code may not work in full accordance with project requirements)
       * 0/3: No error checking (code likely does not work in accordance with project requirements)       * 0/3: No error checking (code likely does not work in accordance with project requirements)
-  * Any and all non-void functions written must have, **at most**, 1 **return** statement+  * Any and all non-void functions written must have exactly 1 **return** statement
     * points will be lost for solutions containing multiple return statements in a function.     * points will be lost for solutions containing multiple return statements in a function.
   * Absolutely, positively **NO** (as in **ZERO**) use of **goto** statements.   * Absolutely, positively **NO** (as in **ZERO**) use of **goto** statements.
     * points will most definitely be lest for solutions employing such things.     * points will most definitely be lest for solutions employing such things.
   * No custom global variables! The header files provide all you need.   * No custom global variables! The header files provide all you need.
 +    * Do NOT edit the header files.
   * Track/version the source code in a repository   * Track/version the source code in a repository
   * Filling out any submit-time questionnaires   * Filling out any submit-time questionnaires
   * Submit a copy of your source code to me using the **submit** tool (**make submit** will do this) by the deadline.   * Submit a copy of your source code to me using the **submit** tool (**make submit** will do this) by the deadline.
haas/fall2016/common/submitblurb.1503866631.txt.gz · Last modified: 2017/08/27 20:43 by wedge