======Part 1======

=====Entries=====
====Entry 1: August 31st, 2012====

Got told today that my wonderful idea from last semester's C/C++ is no longer a wonderful idea due to the fact that I know more about C...

Well, that was definetly fine, but now I have to come up with another good idea, first idea was to use our project big num, but I can't think of some way to put those numbers into the array for it  yet.  But that is a possible way to do it.  I will have to keep thinking about this.
====Entry 2: September 5th, 2012====

Displaying numbers as hex, why did I not think of this...

Ohh, that is why, I dislike displaying numbers outside of decimal numbers (aka base 10).  Guess I am going to have to attempt to learn to read hexidecimal now gah...
====Entry 3: September 12th, 2012====

Still not 100% sure how I am going to mess around with the hex to decimal bignum thingy...  I am confused on how to get the hexidecimal into variables.  But I have decided how to turn the hexidecimal into decimal.
====Entry 4: September 18th, 2012====

Realized I forgot to do the function part of our work that we needed for discrete today.  I guess that is what I get for not paying attention
=====Keywords=====

{{page>datapart1&nofooter}}

{{page>discretepart1&nofooter}}

{{page>unixpart1&nofooter}}

=====Experiment 1=====

====Question====
In unix's ViM, does :1m$ do the same thing as :0m$?

====Resources====
Basic knowledge with the unix system and ViM is very helpful in helping you understand how this will work.
====Hypothesis====
I hypothesis that it will move the 1st line and do the same thing.  Line 0 can be the same as line 1.
====Experiment====
I am going to make a vim text file and just use the commands.

Create a file, put in a bunch of none repeating jibberish and run the first command, and then recreate the same jibberish, and run the second command, and then compare.
====Data====
This is the vi file I used for my start point
<cli>
There is going to be stuff we are doing.
where we need a good chunk of space per line.
So here I am typing a bunch of jibberish lines of text.
and i don't know what we are doing yet so.
I will keep typing until matt says we can stop.
Okay I think a 7th line is way more than enough lines.
http://www.google.com/
ohh my, ohh my gosh.
hi.
</cli>

Next we will run the :0m$ command
<cli>where we need a good chunk of space per line.
So here I am typing a bunch of jibberish lines of text.
and i don't know what we are doing yet so.
I will keep typing until matt says we can stop.
Okay I think a 7th line is way more than enough lines.
http://www.google.com/
ohh my, ohh my gosh.
hi.
there is going to be stuff we are doing.
</cli>
This is my results after running the command :om$
It appears it moved the first line to the last line of the file.

Next lets run the :1m$ command
<cli>
where we need a good chunk of space per line.
So here I am typing a bunch of jibberish lines of text.
and i don't know what we are doing yet so.
I will keep typing until matt says we can stop.
Okay I think a 7th line is way more than enough lines.
http://www.google.com/
ohh my, ohh my gosh.
hi.
there is going to be stuff we are doing.
</cli>

The experiment has shown that the two commands act the same.
Perform your experiment, and collect/document the results here.

====Analysis====
Based on the data collected:
My hypothesis is correct and the commands worked as expected.
====Conclusions====
I have concluded that ViM does not use programming based counting for its lines (starting at 0).