Lab46 Wiki

User Tools

Site Tools

You are here: start » haas » fall2020 » discrete » projects » bdt2
haas:fall2020:discrete:projects:bdt2

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:fall2020:discrete:projects:bdt2 [2020/09/29 21:59] – [Basic functionality] wedgehaas:fall2020:discrete:projects:bdt2 [2020/09/30 16:35] (current) – [Implementation Restrictions] wedge
Line 63: Line 63:
     * **justification** implies some thoughtful why/how style comments explaining how a particular use of one of these statements is effective and efficient (not: "I couldn't think of any other way to do it").     * **justification** implies some thoughtful why/how style comments explaining how a particular use of one of these statements is effective and efficient (not: "I couldn't think of any other way to do it").
   * absolutely **NO** infinite loops (**while(1)** or the like).   * absolutely **NO** infinite loops (**while(1)** or the like).
 +  * ALL variables must be well and pertinently named, and be no fewer than 4 symbols in length
   * 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 telling; no "ungetting" data back into the file).   * 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 telling; no "ungetting" data back into the file).
   * 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.
Line 110: Line 111:
        environment, or NULL if there is no match.        environment, or NULL if there is no match.
 </cli> </cli>
 +
 +Your "const char *name" is the name of the variable set (for the purposes of this project, call it **THROTTLE**). Check the example execution to see it in use. 
  
 You may notice similarity in parameter usage to that of other standard library functions that you've utilized, like **atoi(3)**. You may notice similarity in parameter usage to that of other standard library functions that you've utilized, like **atoi(3)**.
 +
 +**NOTE:** You may **not** want to nest your **getenv(3)** call as a parameter to **atoi(3)**; in the event of an error (or no such variable being set), a NULL tends to cause a segmentation fault.
 =====Reference Implementations===== =====Reference Implementations=====
 To assist you in your off-system development efforts, the **bin/** directory in the bdt2 project (available on lab46 via grabit) has 2 compiled binaries: To assist you in your off-system development efforts, the **bin/** directory in the bdt2 project (available on lab46 via grabit) has 2 compiled binaries:
Line 162: Line 167:
  
 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.
 +
 +What I will be looking for:
  
 <code> <code>
-182:bdt2:final tally of results (182/182)+195:bdt2:final tally of results (195/195)
 *:bdt2:bdt2.c compiles cleanly, no compiler messages [13/13] *:bdt2:bdt2.c compiles cleanly, no compiler messages [13/13]
 *:bdt2:bdt2.c implements only specified algorithm [26/26] *:bdt2:bdt2.c implements only specified algorithm [26/26]
Line 173: Line 180:
 *:bdt2:bdt2 runtime output conforms to reference [26/26] *:bdt2:bdt2 runtime output conforms to reference [26/26]
 *:bdt2:bdt2 runtime output matches reference [26/26] *:bdt2:bdt2 runtime output matches reference [26/26]
-*:bdt2:bdt2 committed, pushed to lab46 repository [13/13]+*:bdt2:bdt2 committed, pushed to lab46 repository [26/26]
 </code> </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 are subject to a 25% overall deduction
haas/fall2020/discrete/projects/bdt2.1601416780.txt.gz · Last modified: 2020/09/29 21:59 by wedge

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki