With the next developer release, 1.1.3 out of the door, the focus goes back to bug fixing, patching up platforms like m68k-netbsd, or cygwin, and improving support for Eclipse, as well as getting JBoss 3.2.x to run better.

Tomcat 5 is also on the list of apps, I'd like to see running well on the next release, due in 2 months.

Currently I'm fighting with a really bizarre crash on Cygwin : a function gets its first few bytes modified somehow. No idea why it happens, but the disassembly when I get the SIGSEGV is different from the disassembly before I run kaffe. Setting watches on the function didn't help.

The other bizarre problem is some broken assembler code on m68k, well hidden in a C macro. So now I'm slowly turning macros into inline functions and silently cursing whoever decided against using inline functions in the first place.

RCS tags are evil

RCS tags are those cute $Date, $Id, $Log etc tags you find in people's source code. The upside is that they are meant to give you easy access to versioning information. The downside is that they give you tons of bad diffs as soon as there is more than one person working on the project, or even worse, another project decides to import your sources.

RCS tags in CVS projects don't give you anything that the cvs command can't tell you on demand, without wasting space with redundant information in source files. RCS tags are so old fashioned, you better get rid of them today before someone looks at your code!