I've got the unit tests of the signals running under both Windows XP and Mac OS X. I installed Code::Blocks on the MacBook Pro so that I'd be using the same IDE on both machines and the projects files are (mildly) compatible. I've still had to use separate project files for both systems as the dire…

What secret competition theme will the cards reveal?



Now all I have to do is find a good way to map the cards to themes we can actually use. And come up with a good competition name based on cartomancy - any suggestions?

My signal memory manager has now been adapted to use Boost.pool instead of my hacked up std::vector version. It involved a rewrite of most of the way the internal lists were handled, but it seems to be working again. I suspect there were a few undefined pointers in there that were causing the origi…

Using Boost's test library I've crafted together a unit testing framework for black box testing of my library components. To start with I've written a couple of test cases for the signal system.

My tests so far have been successful. And by "successful", I mean they found an annoying memory allocatio…

It's Monday morning, and the start of a new week.

Review of productivity last week: I seemed to be getting things done, but if you look at the number of crossed off items at the top of the journal it proves otherwise. My grand total of completed list items last week was... one. Just one. And that on…

It's Sunday, which means it's now four weeks to the start of the competition. I've made another post in the Lounge asking for ideas. According to my roughly pencilled in timetable for this competition I'll need to finalise how this thing is going to be run by next Sunday, so there's a fair bit of p…

Yet another double entry from me today. My last addition to the previous entry stated that I'd finished with the signal and event system, and as such I'd crossed it off my list of things to do. However I'm uncomfortable with the adhoc testing I've given the system so far given how critical it will …

I hope I'm not boring everyone to death with my signal coding adventures. I suppose it's a bit dry but hopefully this hurdle will be overcome soon.

I've cleaned up the code for the signals a little bit, structured them across a number of header files, put in some namespaces and fixed my project dire…

It seems my initital confidence in the performance of my signal code was misplaced. Once I put in the disconnections capabilities I realised I'd missed a few details to do with the double linked list in the memory block, and with some extra guards I need to throw in it now is a bit slower than my i…

I was feeling a bit crook this morning so I decided to work on coding up the signal system rather than decipher more research papers. The prototype code I have now is ugly as sin in parts - partly due to my savage beating of C++'s strongly typed system with blunt objects - but it appears to be work…