User Tools

Site Tools


haas:fall2018:discrete:projects:bdt0

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:fall2018:discrete:projects:bdt0 [2018/08/26 13:14] – [Submission] wedgehaas:fall2018:discrete:projects:bdt0 [2018/08/26 13:20] (current) – [Submission] wedge
Line 263: Line 263:
   * no forced redirection of the flow of the process (no seeking to the end of the file to grab a max size only to zip back somewhere else: deal with the data in as you are naturally encountering it).   * no forced redirection of the flow of the process (no seeking to the end of the file to grab a max size only to zip back somewhere else: deal with the data in as you are naturally encountering it).
   * With the exception of any negative values, all numbers should be transacted in hexadecimal (as in the values you assign and compare and manipulate in your code).   * With the exception of any negative values, all numbers should be transacted in hexadecimal (as in the values you assign and compare and manipulate in your code).
-  * No line must exceed 80 characters in width.+  * No line of output must exceed 80 characters in width
 +    * For code readability, note that my terminals are generally 90 characters wide. You may want to format your code to reduce line-wrappings, inadvertently making your source code less readable
   * All "arrays" must be declared and referenced using ONLY pointer notation, NO square brackets.   * All "arrays" must be declared and referenced using ONLY pointer notation, NO square brackets.
   * For the highlighted address and lengths, store them in an array of structs (containing the //address// and //length// members).   * For the highlighted address and lengths, store them in an array of structs (containing the //address// and //length// members).
Line 305: Line 306:
  
 You should get some sort of confirmation indicating successful submission if all went according to plan. If not, check for typos and or locational mismatches. You should get some sort of confirmation indicating successful submission if all went according to plan. If not, check for typos and or locational mismatches.
 +
 +=====Evaluation Criteria=====
 +
 +What I will be looking for:
 +
 +<code>
 +130:bdt0:final tally of results (130/130)
 +*:bdt0:bdt0.c compiles cleanly, no compiler messages [13/13]
 +*:bdt0:bdt0.c implements only specified algorithm [13/13]
 +*:bdt0:bdt0.c code conforms to project specifications [26/26]
 +*:bdt0:bdt0.c implementation free from restrictions [13/13]
 +*:bdt0:bdt0 runtime output conforms to specifications [26/26]
 +*:bdt0:bdt0 make check tests succeed [13/13]
 +*:bdt0:bdt0 make checklines tests succeed [13/13]
 +*:bdt0:bdt0 make checkcolors tests succeed [13/13]
 +</code>
 +
 +Additionally:
 +  * Solutions not abiding by spirit of project will be subject to a 25% overall deduction
 +  * Solutions not utilizing descriptive why and how comments will be subject to a 25% overall deduction
 +  * Solutions not utilizing indentation to promote scope and clarity will be subject to a 25% overall deduction
 +  * Solutions not organized and easy to read (assume a terminal at least 90 characters wide, 40 characters tall) are subject to a 25% overall deduction
haas/fall2018/discrete/projects/bdt0.1535289257.txt.gz · Last modified: 2018/08/26 13:14 by wedge