======Part 3====== =====Entries===== ====Entry 9: April 5, 2012==== Today we learned about logic gates and classes. We used classes to allow us to create separate files each containing a part of the program. This allows for organization and simple finding because instead of having to search a single program you can just look for the file of which one would hope was named after what it does. Ex. got a function that checks two variables for if they are both true. you would name this separate file "and.cc" not "phill" as "and.cc" is actually what it checks for. ====Entry 10: April 10, 2012==== Today i learned that their is actually a changeable file for the vi system. This was really cool for me because one of my biggest problems with vi is that it was to dull and sometimes hard to read sometimes after staring for a while. This also was cool because it demonstrates that once again everything and every program is a file. ====Entry 11: April 24, 2012==== Templates - a tool for generic programming in c++ They allow for a generic representation of a process that gets specific when you use it. Its kind of like a stencil for a program. A stencil can fit different types of coloring utensils so in that aspect a template can support different types of variables from chars to ints. this includes April 30 - May 9, 2012 (the opus does not allow me to edit the fourth journal day so i am putting it here) procrastination kills. Let this be a warning unto myself if i pass this class i will be happy. The issue is that i keep putting off this class work in order to allow myself the ability to finish other work and running out of time with this class. New priority this stuff is my life nuff said i need to focus on my programming because this will be my future. i also have really bad eye irritation and need some gunnar glasses so this doesn't hurt so much. ====Entry 12: April Day, 2012==== This is a sample format for a dated entry. Please substitute the actual date for "Month Day, Year", and duplicate the level 4 heading to make additional entries. As an aid, feel free to use the following questions to help you generate content for your entries: * What action or concept of significance, as related to the course, did you experience on this date? * Why was this significant? * What concepts are you dealing with that may not make perfect sense? * What challenges are you facing with respect to the course? Remember that 4 is just the minimum number of entries. Feel free to have more. {{page>cprogpart3&nofooter}} =====Experiments===== ====Experiment 7==== ===Question=== in an while statement can i subtract 48 from /n in the controller of the loop? ===Resources=== none previous knowledge ===Hypothesis=== Yes, I should be able to treat the variables like they were somewhere else and not special. ===Experiment=== I am going to use a while loop and i wanted to subtract 48 from the numbers because they were still in ASCII so i did now it wont see the \n that finishes it i will change the end loop variable to '\n'-48 and hope it works ===Data=== while(g!='\n') 52 { 53 g = fgetc(stdin); 54 g = g-48; 55 arr2[f] = g; 56 f = f + 1; 57 } while(g!='\n'-48) 52 { 53 g = fgetc(stdin); 54 g = g-48; 55 arr2[f] = g; 56 f = f + 1; 57 } this worked ===Analysis=== Based on the data collected: * Was your hypothesis correct? * yes * Was your hypothesis not applicable? * yes * Is there more going on than you originally thought? (shortcomings in hypothesis) * not that i can tell but not perfect with loops * What shortcomings might there be in your experiment? * my lack of knowledge of loops ===Conclusions=== This works and is a great way to help with math functions in a program. ====Experiment 8==== ===Question=== What is the question you'd like to pose for experimentation? State it here. ===Resources=== 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. ===Hypothesis=== 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. ===Experiment=== How are you going to test your hypothesis? What is the structure of your experiment? ===Data=== Perform your experiment, and collect/document the results here. ===Analysis=== 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? ===Conclusions=== 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. ====Retest 3==== Perform the following steps: ===State Experiment=== Whose existing experiment are you going to retest? Provide the URL, note the author, and restate their question. ===Resources=== Evaluate their resources and commentary. Answer the following questions: * Do you feel the given resources are adequate in providing sufficient background information? * Are there additional resources you've found that you can add to the resources list? * Does the original experimenter appear to have obtained a necessary fundamental understanding of the concepts leading up to their stated experiment? * If you find a deviation in opinion, state why you think this might exist. ===Hypothesis=== State their experiment's hypothesis. Answer the following questions: * Do you feel their hypothesis is adequate in capturing the essence of what they're trying to discover? * What improvements could you make to their hypothesis, if any? ===Experiment=== Follow the steps given to recreate the original experiment. Answer the following questions: * Are the instructions correct in successfully achieving the results? * Is there room for improvement in the experiment instructions/description? What suggestions would you make? * Would you make any alterations to the structure of the experiment to yield better results? What, and why? ===Data=== Publish the data you have gained from your performing of the experiment here. ===Analysis=== Answer the following: * Does the data seem in-line with the published data from the original author? * Can you explain any deviations? * How about any sources of error? * Is the stated hypothesis adequate? ===Conclusions=== Answer the following: * What conclusions can you make based on performing the experiment? * Do you feel the experiment was adequate in obtaining a further understanding of a concept? * Does the original author appear to have gotten some value out of performing the experiment? * Any suggestions or observations that could improve this particular process (in general, or specifically you, or specifically for the original author).