_Jonathan Leto wrote:_
This wayward son is still on his treacherous journey to increase
"test coverage in src/extend_vtable.c":https://github.com/parrot/parrot/blob/master/t/src/extend_vtable.t. When we last left off our traveler, he explained what the mythical VTABLE beast looked like, and we shall continue with the study of this chimerical fauna.
According to the latest code coverage statistics, we are now at "64% code coverage":http://tapir2.ro.vutbr.cz/cover/latest-c_cover/src-extend_vtable-c.html, which is an increase of about 10% since my last report.
Most of this grant work concentrated on vtables that required "Key PMCs":http://docs.parrot.org/parrot/devel/html/src/pmc/key.pmc.html. A Key PMC is an object that can be used to look something up in a "Hash PMC":http://docs.parrot.org/parrot/devel/html/src/pmc/hash.pmc.html or other aggregated object that supports "keyed access". It is very much similar to a "hash key" that can be used to look up the appropriate value.
One of the lessons that I have learned in working on these tests is that it is very easy to write tests that pass on gcc, but which "absolutely explode with g++":http://trac.parrot.org/parrot/ticket/2084. This has to do with gcc not being as strict when some questionable type casting is done. I have learned my lesson and I promise not to break the test suite anymore. I will use g++ in my testing from now one, promise!
My productivity was definitely hampered by moving to a new house and having a two week business trip in the last month, but my new home office is finally set up, so I expect productivity to approach previous levels of adding a few dozen tests per week.
_Original article at "dukeleto.pl":http://leto.net/dukeleto.pl/2011/04/parrot-embed-grant-update-4-the-journey-continues.html ._