Mar
12
2009

FYP Development: Using LOC as a measure of progress

Yesterday I talked about how I cut a lot of useless operations in my code. In fact, after all my work yesterday, the codebase is 160 lines shorter!

Last night I was thinking of a few places where things aren’t so snappy, and realised a point where I was overdoing multithreading. What I was doing is taking collision callbacks and putting them onto a job queue do be processed by my own worker threads. In fact, I’m also using Havok multithreading as it is and it’ll already queue up Havok-related operations to be processed by its own worker threads. Removing the useless “threaded” collision callback code meant I removed 4 files from the codebase and dropped another hundred lines or so. And it runs faster!

So in a few days of work, I’ve written -260 lines of code. And I just reminded myself of this old Apple story.

I feel pretty bad talking about “faster” and “snappier” without having my profiling set up yet. I’m on the Havok forums right now trying to get some help with getting timers set up. For some reason, my own Havok timers aren’t working, but Havok’s internal ones are. … But their code ought to be the same as mine so surely it’s an all or nothing thing.. hum.

Written by in: University |

No Comments »

RSS feed for comments on this post. TrackBack URL


Leave a Reply

Powered by WordPress | Theme: Aeros 2.0 by TheBuckmaker.com