User Tools

Site Tools


haas:spring2014:cprog:projects:helloworld

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:spring2014:cprog:projects:helloworld [2014/01/12 18:37] – [Change into your cprog directory] wedgehaas:spring2014:cprog:projects:helloworld [2014/01/27 14:58] (current) – [Verify submission] wedge
Line 1: Line 1:
 +<WRAP centeralign round box>
 +<WRAP><color red><fs 200%>Corning Community College</fs></color></WRAP>
 +<WRAP><fs 150%>CSCS1320 C/C++ Programming</fs></WRAP>
 +</WRAP>
 +
 +~~TOC~~
 +
 ======Hello, World! (first program, and development cycle)====== ======Hello, World! (first program, and development cycle)======
  
Line 244: Line 251:
   * http://en.wikibooks.org/wiki/C_Programming/Compiling   * http://en.wikibooks.org/wiki/C_Programming/Compiling
  
-The nature of compilers themselves can warrant entire courses unto themselves. If you go on in Computer Science, at the 3rd/4th year or graduate level it is not uncommon to encounter "Compiler Construction" course.+The nature of compilers themselves can warrant entire courses unto themselves. If you go on in Computer Science, at the 3rd/4th year or graduate level it is not uncommon to encounter "Compiler Construction" course.
  
 ====Familiarize yourself with file states==== ====Familiarize yourself with file states====
Line 297: Line 304:
 Now we just have to learn all the various keywords and language rules, and familiarize ourselves with the necessary library functions to pull off even more spectacular solutions to problems. Now we just have to learn all the various keywords and language rules, and familiarize ourselves with the necessary library functions to pull off even more spectacular solutions to problems.
  
-You may want to place your C source code (**hello.c**) in a repository for safe keeping- working with repositories is another helpful programming habit to have.+You will want to place your C source code (**hello.c**) in a repository for safe keeping- working with repositories is another helpful programming habit to have. 
 + 
 +=====Submission===== 
 +To successfully complete this project, the following criteria must be met: 
 + 
 +  * Code must compile cleanly (no warnings or errors) 
 +  * Executed program must display the intended message, exactly as presented, to STDOUT. 
 +  * Output must be correct (as per project specifications) 
 +  * 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 
 +    * have at least 5% of your program consist of **<nowiki>//</nowiki>**-style descriptive comments 
 +  * Output Formatting (including spacing) of program must conform to the provided output (see sample program output above). 
 +  * Track/version the source code in a repository 
 +  * Submit a copy of your source code to me using the **submit** tool. 
 + 
 +To submit this program to me using the **submit** tool, run the following command at your lab46 prompt: 
 + 
 +<cli> 
 +$ submit cprog helloworld hello.c 
 +Submitting cprog project "helloworld": 
 +    -> hello.c(OK) 
 + 
 +SUCCESSFULLY SUBMITTED 
 +</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. 
 + 
haas/spring2014/cprog/projects/helloworld.1389551853.txt.gz · Last modified: 2014/01/12 18:37 by wedge