3 posts tagged “c++”

celtic@sohma:~/code/linux/rubyex/translator$ ./test
test: "identifier": failure: Assertion failed on line 53: p.expressions.size() == 0
1 test(s) run, 0 test(s) succeeded.
celtic@sohma:~/code/linux/rubyex/translator$

これでテストコードがある：
And here we have the test code:

void _identifier()
{
  Program p = parse_code("abc");
  ASSERT(p.expressions.size() == 0);
}

The next question, of course, is of the best way to test parsers written in bison. I could just put all the parsing code in a separate library and have it compile two programs instead of the one big thing (i.e. one the parser, one the testing parser which just asserts all the output). I have no idea about test frameworks for C or C++, so I'll have a look now, I think.

I've been doing a bit of dev on the Nintendo DS recently, courtesy of the M4 I purchased ages ago, on a bit of a whim. I'm glad to say I've actually gotten into it now, though.

The graphics hardware is slightly confusing, since you have to draw to two different screens, either one of which may programmatically be considered the `main' and the other the `sub' screen. You also set up different video modes for either, with tile/2D/3D/framebuffer options, though the 3D engine only operates on one screen at a time (but you can do a hackish thing to render to both). The 3D is actually very cool, since the interface mimics OpenGL's interface very closely.

It has two CPUs, an ARM7 and an ARM9. This makes coding interesting, as the ARM7 is the one which can access the majority of the hardware, and the ARM9 is the one you end up using for most of your logic [more powerful/faster/etc. maybe. it's what I was taught to do.]. Thus, IPC (interprocess communication) ends up being fairly important as you try to talk between the two CPUs and keep things synchronised. I'm using libnds as my C/C++ wrapper/library/thing to code for the DS, and it seems to make much of the IPC and setting up things like IRQs fairly straight forward, but we'll see what happens when I get down to writing wifi code or similar.

I'm starting fairly basic, with a 'reflex timer' game where circles appear and you have to hit them quickly. Top screen displays statistics for now. I'll take a screenshot when it's a bit more developed. I'm moving along fairly quickly, so hopefully things should be awesome.

I was pleasantly surprised to note that using things like the STL is fine, since it's all statically linked anyway.