=====cprog Keywords=====
====(standard I/O)====
Standard I/O 

===Definition===
Standard In and Standard Out. Standard In is usually the key board, standard out is usually the monitor. 

===Demonstration===
Demonstration of the chosen keyword.

If you wish to aid your definition with a code sample, you can do so by using a wiki **code** block, an example follows:

<code c>
/*
 * Sample code block
 */
#include <stdio.h>

int main()
{
printf("dafsf");
scanf("fda");
    return(0);
}
</code>



====(Header files)====
Header files

===Definition===
are files that are include in the main file, that have data in another file.

===Demonstration===
Demonstration of the chosen keyword.

If you wish to aid your definition with a code sample, you can do so by using a wiki **code** block, an example follows:

<code c>
/*
 * Sample code block
 */
#include <stdio.h>


</code>



====(pointers)====
pointers

===Definition===
pointers are used to refer to a memory location of another variable, with out using that variable identifier.

===Demonstration===
Demonstration of the chosen keyword.

If you wish to aid your definition with a code sample, you can do so by using a wiki **code** block, an example follows:

<code c>
/*
 * Sample code block
 */
#include <stdio.h>
int *chicken
int main()
{
    return(0);
}
</code>


====(variables)====
variables
===Definition===
variables are place holders for a values that are in memory. 

===Demonstration===
Demonstration of the chosen keyword.

If you wish to aid your definition with a code sample, you can do so by using a wiki **code** block, an example follows:

<code c>
/*
 * Sample code block
 */
#include <stdio.h>
int chicken
char turkey
int main()

</code>


====(scope)====
scope

===Definition===
place in the declaration where a variables name can be used


====(array)====
array

===Definition===
a way of organizing a collection of related data, using a variable name


====(type casting)====
type casting

===Definition===
making a one type of variable act like another type of variable for a single operation.


====(arithmetic)====
arithmetic

===Definition===
(+)(-)(*)(/)(%)

===Demonstration===
Demonstration of the chosen keyword.

If you wish to aid your definition with a code sample, you can do so by using a wiki **code** block, an example follows:

<code c>
/*
 * Sample code block
 */
#include <stdio.h>

int main()
{
    return(0);
}
</code>

Alternatively (or additionally), if you want to demonstrate something on the command-line, you can do so as follows:

<cli>
lab46:~$ cd src
lab46:~/src$ gcc -o hello hello.c
lab46:~/src$ ./hello
Hello, World!
lab46:~/src$ 
</cli>

=====cprog Objective=====
====cprog Objective====
Upon completion of this course, students will be able to:

-write and compile code that utilizes programming constructs
-use pointers and variables to discover the indirect properties of data storage
-comprehend the basics of memory management, data representation and storage
-identify and label various data types as scalar vs. composite
-distinguish and explain difference between homogeneous and heterogeneous composite data types
-break down and separate code into functions and illustrate the use of parameter passing
-justify the use of various programming constructs within code solutions
-discover the standard libraries and use libraries in solving problems

===Definition===
students should be able to 
-Write programs
-use pointers effectively 
-understand what memory management is.
-use the different data types
-use the different libraries to do what your trying to do
===Method===
I will be measuring my success in this class on whether or not i will be able to complete the projects.

===Measurement===
According to my method, i am understanding the basics of what i need to do, but when it comes to putting it all together in a programs by my self, i am only able to do about have of it. I end up needing to get assistance from Matt or class mates.

===Analysis===
Reflect upon your results of the measurement to ascertain your achievement of the particular course objective.

  * i am doing pretty good
  * there is definitively room for improvement
  * i think my method is a pretty good way to measure success