Gilbert’s blag

Group E

Expected 6 hours

Actual 13 hours

==4115== Memcheck, a memory error detector.
==4115== Copyright (C) 2002-2008, and GNU GPL’d, by Julian Seward et al.
==4115== Using LibVEX rev 1878, a library for dynamic binary translation.
==4115== Copyright (C) 2004-2008, and GNU GPL’d, by OpenWorks LLP.
==4115== Using valgrind-3.4.0, a dynamic binary instrumentation framework.
==4115== Copyright (C) 2000-2008, and GNU GPL’d, by Julian Seward et al.
==4115== For more details, rerun with: -v
==4115==
……

OK (6 tests)

==4115==
==4115== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 21 from 1)
==4115== malloc/free: in use at exit: 122,880 bytes in 6 blocks.
==4115== malloc/free: 868 allocs, 862 frees, 195,925 bytes allocated.
==4115== For counts of detected errors, rerun with: -v
==4115== searching for pointers to 6 not-freed blocks.
==4115== checked 124,140 bytes.
==4115==
==4115== LEAK SUMMARY:
==4115==    definitely lost: 0 bytes in 0 blocks.
==4115==      possibly lost: 0 bytes in 0 blocks.
==4115==    still reachable: 122,880 bytes in 6 blocks.
==4115==         suppressed: 0 bytes in 0 blocks.
==4115== Rerun with –leak-check=full to see details of leaked memory.

Partner: Jason Tsay

Expected: 5

Actual : 7

Expected time : 6 hours

Actual time : 7 hours

Group 54865E

==11690== Memcheck, a memory error detector.
==11690== Copyright (C) 2002-2008, and GNU GPL’d, by Julian Seward et al.
==11690== Using LibVEX rev 1878, a library for dynamic binary translation.
==11690== Copyright (C) 2004-2008, and GNU GPL’d, by OpenWorks LLP.
==11690== Using valgrind-3.4.0, a dynamic binary instrumentation framework.
==11690== Copyright (C) 2000-2008, and GNU GPL’d, by Julian Seward et al.
==11690== For more details, rerun with: -v
==11690==
…………………..

OK (23)
==11690==
==11690== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 21 from 1)
==11690== malloc/free: in use at exit: 122,880 bytes in 6 blocks.
==11690== malloc/free: 1,060 allocs, 1,054 frees, 360,670 bytes allocated.
==11690== For counts of detected errors, rerun with: -v
==11690== searching for pointers to 6 not-freed blocks.
==11690== checked 124,136 bytes.
==11690==
==11690== LEAK SUMMARY:
==11690==    definitely lost: 0 bytes in 0 blocks.
==11690==      possibly lost: 0 bytes in 0 blocks.
==11690==    still reachable: 122,880 bytes in 6 blocks.
==11690==         suppressed: 0 bytes in 0 blocks.
==11690== Rerun with –leak-check=full to see details of leaked memory.

Partner : Yuanle Song

Expected time: 5 hours

Actual time : 6 hours

This week was ok. We had to work on Faculty2, which was a confusing project, having to get google app running, having to figure out what the final xml data was gonna be and how to extract that xml in python using beatiful soup.

Aside from that, the rest of the week was pretty good. Seeing the refactoring example was interesting, seeing how it was changed slowly piece by piece. Although, I would have also liked if we looked over SQL some more, as I don’t know a lot of SQL and would have found that interesting and useful for me.

Overall, I liked what we learned this week and hope I can have another good week.

Bye blag

GC

This week was a fun week in OOP. We learned about operator overloading, which was really a fuzzy subject in my head until we went over it. Also, we learned about conversions C++ does, which I had no clue about until we reviewed it and was really interesting. We also learned about copy assignment, so overall, I learned a good deal and was able to see many things I really didn’t know about.

The Sudoku project went ok, Yuangle was a really great partner and showed me a lot of stuff I didn’t know about.

It was a good week,

GC

Our presentation went well this week. Most people did a good job, although our scheme probably isn’t as good as it could be. We probably need to work on that some more. Although it is kinda hard knowing when it is ok to repeat data or not, since in the end, we will either have more complicated queries or lots of repeated data.

Also, it has been hard knowing what we can actually do without a unified xml scheme. Although, aside from that, the project is going well (although we don’t really know how to use the google app engine yet). Hopefully we can get everything done this week.

I think I should probably go finish that reading now.

-GC

So, this week there was no project due. The sudoku project doesn’t seem like it will be too tough but I will probably get started soon so my weekend isn’t wasted on trying to find bugs.

Finally got the test grade back this week, I did pretty well but still have room for improvement. I think I had to rush too much which lead to some mistakes but I will be ready next time.

We learned some interesting things, at least now I understand what those friend functions are for. Also, seeing how we have to overload methods, I see why java does not have a const in it. Now, I should go do that reading for this week.

-GC