Difference between revisions of "User:Hcurtis0010/GSoC2014/logs"
Hcurtis0010 (talk | contribs) (→Week 1) |
Hcurtis0010 (talk | contribs) m (→Week 1) |
||
| Line 19: | Line 19: | ||
I showed to the community the program that I completed yesterday, and I received feedback on it. That evening, I worked on the second program, the one that had been giving me problems. In it I used malloc() for the first time. At first it wouldn't compile, and later it would compile but would crash at runtime. However, I finally got it to work after a fellow GsoCer, Raj12lnm, told me what I was doing wrong. | I showed to the community the program that I completed yesterday, and I received feedback on it. That evening, I worked on the second program, the one that had been giving me problems. In it I used malloc() for the first time. At first it wouldn't compile, and later it would compile but would crash at runtime. However, I finally got it to work after a fellow GsoCer, Raj12lnm, told me what I was doing wrong. | ||
| − | The work I did today is preparing me to address problems with BRL-CAD’s fast4-g.c program as well as the conversion libraries that are the focus of my GSoC proposal. We'll see how it goes. | + | The work I did today is preparing me to address problems with BRL-CAD’s fast4-g.c program as well as produce the conversion libraries that are the focus of my GSoC proposal. We'll see how it goes. |
Revision as of 05:30, 22 May 2014
Week 1
Monday, May 19
I re-read the Hacking file, and that led me to do research on binaries, regression testing, and other topics. Also, I had a good IRC conversation with my mentor, Sean Morrison, about how best to interact with one another and what I will need to do to succeed during GSoC.
Tuesday, May 20
Sean and I had an enlightening IRC conversation in which he pointed out the danger of relying too much on examples when dealing with code.
Afterward, I wrote some programs involving arrays. Although I finished the first one, I ran into problems with the second. I did some research as I attempted to solve it; the topics I investigated included dynamic allocation, vectors, and heaps. Sean had asked me to create the programs in order to learn more about dynamic and stack memory and be able to apply that knowledge to future GSoC activities.
Wednesday, May 21
I am happy to say that I learned a lot today. One of the more memorable things I learned was that I should not put the "using namespace" construct in my programs. I conducted research to find out why. Also, I read about malloc(), pointers, and the differences between C and C++.
I showed to the community the program that I completed yesterday, and I received feedback on it. That evening, I worked on the second program, the one that had been giving me problems. In it I used malloc() for the first time. At first it wouldn't compile, and later it would compile but would crash at runtime. However, I finally got it to work after a fellow GsoCer, Raj12lnm, told me what I was doing wrong.
The work I did today is preparing me to address problems with BRL-CAD’s fast4-g.c program as well as produce the conversion libraries that are the focus of my GSoC proposal. We'll see how it goes.
