Differences

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

--- haas:fall2017:cprog:projects:dtr0 [2017/08/20 16:56] – created wedge
+++ haas:fall2017:cprog:projects:dtr0 [2018/02/02 18:42] (current) – wedge
@@ Line 3: / Line 3: @@
 <WRAP><fs 150%>CSCS1320 C/C++ Programming</fs></WRAP>
 </WRAP>
-~~TOC~~
 ======Project: DATA TYPE RANGES (dtr0)======
@@ Line 45: / Line 43: @@
 <code c>
 /*
- * datatypes.c - A program to derive and display information
+ * dtr0.c - A program to derive and display information
- *               for the signed and unsigned data types in C
+ *          for the signed and unsigned data types in C
  *
  *
- * A program by NAME for CSCS1320 COURSE (SEMESTER)
+ * A program by NAME for COURSENUMBER COURSENAME (SEMESTER)
  *
- * Compile with: gcc -o datatypes datatypes.c
+ * Compile with: gcc -o dtr0 dtr0.c
- * Execute with: ./datatypes
+ * Execute with: ./dtr0
  */
@@ Line 103: / Line 101: @@
 <cli>
-lab46:~/src/cprog$ ./datatypes
+lab46:~/src/cprog/dtr0$ ./dtr0
 TYPE: unsigned char, bytes: 1, low: 0, high: 255, qty: 256
 TYPE:   signed char, bytes: X, low: X, high: X, qty: X
@@ Line 109: / Line 107: @@
 TYPE:   signed short int, bytes: X, low: X, high: X, qty: X
 ...
-lab46:~/src/cprog$
+lab46:~/src/cprog/dtr0$
 </cli>
 This output includes some mock additional entries, actual values abstracted. Instead of displaying 'X', your program should display the actual values, and display a total of 10 lines, for the signed and unsigned variations of the five data types we are studying in this project.
 =====Reflection=====
 Be sure to provide any commentary on your journal regarding realizations had and discoveries made during your pursuit of this project. You should also consider adding extra comments into your program so that it can be a more valuable reference going forward.
@@ Line 138: / Line 137: @@
     * signed long long int
-=====Submission=====
+=====Review of Compiling/Executing=====
-To successfully complete this project, the following criteria must be met:
+Just to review the compilation/execution process for working with your source code, if we had a file, **hello.c**, that we wished to compile to a binary called **hello**, we'd first want to compile the code, as follows:
-  * Code must compile cleanly (no warnings or errors)
+<cli>
-  * Executed program must display a total of 10 lines, one for each data type.
+lab46:~/src/cprog/proj$ gcc -Wall --std=c99 -o hello hello.c
-  * Output must be correct, and in its simplest/most reduced form (based on available resources)
+lab46:~/src/cprog/proj$
-    * Each type must show a mathematically correct quantity
+</cli>
-    * high and low values **must** be computed logically
+Assuming there are no syntax errors or warnings, and everything compiled correctly, you should just get your prompt back. In the event of problems, the compiler will be sure to tell you about them.
+Conceptually, the arrangement is as follows:
+<code>
+gcc -Wall --std=c99 -o BINARY_FILE SOURCE_FILE
+</code>
+The BINARY_FILE comes **immediately after** the **-o**, **NOT** the SOURCE_FILE (it must never **immediately** follow a **-o**). It can precede, and such is perfectly valid (especially if you feel that way more intuitive).
+The **-Wall** (treat all warnings as errors, increase general verbosity about warnings) and **--std=c99** (switch compiler to use the **C99** standard of the C language) are options given to the compiler.
+To execute your binary, we need to specify a path to it, so we use **./**, which references the current directory (the dot '.' tells the computer "my current location", and the forward slash '/' is the directory separator):
+<cli>
+lab46:~/src/cprog/proj$ ./hello
+Hello, World!
+lab46:~/src/cprog/proj$
+</cli>
+=====Submission Criteria=====
+To be successful in this project, the following criteria must be met:
+  * Project must be submit on time, by the posted deadline to be eligible for full credit.
+    * Late submissions will lose 25% credit per day, with the submission window closing on the 4th day following the deadline.
+    * Early submissions can earn 1 bonus point per day in advance of the posted due date.
+  * All code must compile cleanly (no warnings or errors)
+    * Use the **-Wall** and **--std=c99** flags when compiling.
+    * all requested functions must be implemented in the related library or program
+    * 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
-    * have a properly filled-out comment banner at the top
+    * Any "to be implemented" comments **MUST** be removed
-    * have at least 20% of your program consist of **<nowiki>//</nowiki>**-style descriptive comments
+      * these "to be implemented" comments, if still present at evaluation time, will result in points being deducted.
-  * Output Formatting (including spacing-- overall field alignment is not needed) of program must conform to the provided output (see unsigned char example above).
+    * Sufficient comments explaining the point of provided logic **MUST** be present
   * Track/version the source code in a repository
-  * Submit a copy of your source code to me using the **submit** tool.
+  * Submit a copy of your source code to me using the **submit** tool by the deadline.
+  * Make sure your submitted source code is in a file called **dtr0.c**
+  * Make sure it outputs exactly like the sample output above.
-To submit this program to me using the **submit** tool, run the following command at your lab46 prompt:
+====Submit Tool Usage====
+Let's say you have completed work on the project, and are ready to submit, you would do the following:
 <cli>
-$ submit cprog dir0 dtr0.c
+lab46:~/src/cprog/dtr0$ submit cprog dtr0 dtr0.c
 Submitting cprog project "dtr0":
     -> dtr0.c(OK)
 SUCCESSFULLY SUBMITTED
+lab46:~/src/cprog/dtr0$
 </cli>
 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.
+I'll be evaluating the project based on the following criteria:
+<code>
+:dtr0:final tally of results (39/39)
+*:dtr0:submitted file called dtr0.c [3/3]
+*:dtr0:committed and pushed dtr0.c to repository [4/4]
+*:dtr0:adequate and consistent indentation in dtr0.c [4/4]
+*:dtr0:sufficient comments in dtr0.c [4/4]
+*:dtr0:utilizes correct and best fit printf format specifiers [4/4]
+*:dtr0:executable runs without issue [4/4]
+*:dtr0:output is correct [4/4]
+*:dtr0:output conforms to project specifications [4/4]
+*:dtr0:adequate modifications in dtr0.c [4/4]
+*:dtr0:no compiler warnings nor errors for dtr0.c [4/4]
+</code>

Lab46 Wiki

User Tools

Site Tools

Differences

Page Tools