First day of class. We went over the syllabus and learned about the opus(EVIL) as well as the portfolio.

We played with linked lists thats all I can remember.

On one of these days Matt let us work on things and he put out small fires and babies.

Today is the last class in the month of September. We are working on stacks at the same time I am working on the opus(EVIL). Matt can't decide what he wants to do. First In Last Out or Last In First Out.

Version Control is a system used to track and control changes to a projects's files, in particular to source code, documentation, and web pages.

Commit- Is used to make a change to a project; more formally, to store a change in the repository in such a way that it can be incorporated into future releases of the project.

Checkout- The process of obtaining a copy of the project from a repository.

Update- To ask that others' commits be incorporated into your local copy of the project; that is, to bring your copy “up-to-date”.

Add- Inputs a file into a list of files to be tracked before a commit is made.

Log- A reminder attached to each commit, describing the nature and purpose of the commit.

Pointers- Point loctations in memory.

Address of- Can be represented by '&' and is what the pointer points to.

Assingment- Points two pointers to the same pointee.

Deferencing- Follows the arrow from the pointer to the pointee.

Void Pointers- Pointers that do not have a type so they can point to any data type.

Pointer Arithmetic - Only addition and subtraction operations are allowed to be conducted on pointers.

ex) cha++;

Array- It is the same concept as pointers, the identifier of an array is equivalent to the address of its first element, as a pointer is equivalent to the address of the first element that it points to.

Null Pointers- A regular pointer of any type which has a special value that indicates that it is not pointing to any valid reference or memory address, the value is the result of type-casting the integer value zero to any pointer type.

Function Pointers- Passing a function as an argument to another function, since these cannot be passed dereferenced in order to declare a pointer to a function we have to declare it like the prototype of the function, except that the name of the function is enclosed between parentheses () and an asterisk is inserted before the name.

ex) (*proto)(char,char);

Static allocation vs. Dynamic allocation- Statically allocated variables have their storage allocated and initialized before main starts running and are not deallocated until main has terminated. Dynamic allocation the program determines how much memory it needs at run time, and allocate exactly the right amount of storage.

Memory allocation (malloc(), new)- malloc is a subroutine for performing dynamic memory allocation in the C and C++ programming languages, though its use in C++ has been largely superseded by operators new and new[]. malloc is part of the standard library for both languages and is declared in the stdlib.h header although it is also declared within the std namespace via C++'s cstdlib header.

Memory De-allocation (free(), delete)- The delete operator calls the destructor of the given argument, and returns memory allocated by new back to the group. A call to delete must be made for every call to new to avoid a memory leak. After calling delete the memory object pointed to is invalid and should no longer be used. Many programmers assign 0 (null pointer) to pointers after using delete to help minimize programming errors.

Structures- A structured type that aggregates a fixed set of labelled objects, possibly of different types, into a single object. A struct declaration consists of a list of fields, each of which can have any type. The total storage required for a struct object is the sum of the storage requirements of all the fields, plus any internal padding.

Structure pointer- Pointers can be used to refer to a struct by its address. This is particularly useful for passing structs to a function by reference.

Linked Lists- a way to store data with structures so that the programmer can automatically create a new place to store data whenever necessary.

Discuss the representation and use of primitive data types and built-in data structures

How well I have done understanding what we have done in class.

What I have learned is how to make and edit a linked list.

• Not that got to start.
• There is a lot of room for imporvement.
• Yes.
• Yes.
• Tell exectly what we will learn in it.

What is the question you'd like to pose for experimentation? State it here.

Collect information and resources (such as URLs of web resources), and comment on knowledge obtained that you think will provide useful background information to aid in performing the experiment.

Based on what you've read with respect to your original posed question, what do you think will be the result of your experiment (ie an educated guess based on the facts known). This is done before actually performing the experiment.

State your rationale.

How are you going to test your hypothesis? What is the structure of your experiment?

Perform your experiment, and collect/document the results here.

Based on the data collected:

• was your hypothesis correct?
• was your hypothesis not applicable?
• is there more going on than you originally thought? (shortcomings in hypothesis)
• what shortcomings might there be in your experiment?
• what shortcomings might there be in your data?

What can you ascertain based on the experiment performed and data collected? Document your findings here; make a statement as to any discoveries you've made.

What is the question you'd like to pose for experimentation? State it here.

Collect information and resources (such as URLs of web resources), and comment on knowledge obtained that you think will provide useful background information to aid in performing the experiment.

Based on what you've read with respect to your original posed question, what do you think will be the result of your experiment (ie an educated guess based on the facts known). This is done before actually performing the experiment.

State your rationale.

How are you going to test your hypothesis? What is the structure of your experiment?

Perform your experiment, and collect/document the results here.

Based on the data collected:

• was your hypothesis correct?
• was your hypothesis not applicable?
• is there more going on than you originally thought? (shortcomings in hypothesis)
• what shortcomings might there be in your experiment?
• what shortcomings might there be in your data?

What can you ascertain based on the experiment performed and data collected? Document your findings here; make a statement as to any discoveries you've made.

What is the question you'd like to pose for experimentation? State it here.

Collect information and resources (such as URLs of web resources), and comment on knowledge obtained that you think will provide useful background information to aid in performing the experiment.

Based on what you've read with respect to your original posed question, what do you think will be the result of your experiment (ie an educated guess based on the facts known). This is done before actually performing the experiment.

State your rationale.

How are you going to test your hypothesis? What is the structure of your experiment?

Perform your experiment, and collect/document the results here.

Based on the data collected:

• was your hypothesis correct?
• was your hypothesis not applicable?
• is there more going on than you originally thought? (shortcomings in hypothesis)
• what shortcomings might there be in your experiment?
• what shortcomings might there be in your data?

What can you ascertain based on the experiment performed and data collected? Document your findings here; make a statement as to any discoveries you've made.