OK, so I got this insane project in the works that does all sorts of magical transformations on the ludicrous crap compilers spit out.
Its generic in nature - throw any OBJ's at it, 16 bit, 32 bit, from any vendor. Assembler, C/C++, Pascal, Fortran, COBOL, BASIC, whatever, I don't care. I'll make sense of it and rewrite the retard compiler's output into something better.
Pretty heady intricate stuff, altering the output from compilers. The vast majority of programmers never even look at what their compilers are puking out let alone think about trying modify it, but that's the kind of project I like. Bit banging, low level and VERY NASTY where there's zero wiggle room, and hand waving don't cut it. What you do is either 100% right on or its flat out broken.
The past few days I've been working on a fixup optimizer. Its non-trivial since fixups and their plethora of variations and permutations are genuinely nasty and difficult. There's a ton of bits in record fields that have all sorts of different meanings depending on the settings of other bits, sometimes an index is present, sometimes not, sometimes there is a displacement, sometimes not, blah, blah, blah.
Working with fixups is like the "twisty little mazes" in the old Adventure game. Its easy to get in, not so easy to get out, and your head is on a swivel reading spec pages trying to find the exit.
So I whipped out about 1,000 lines of code to do some of these fixup optimizations and wonder of wonders it worked 100% on the first shot. Its not often that you crank out 1,000 lines of crazy intricate code in a few days that works on the first go and continued to work against the outputs from about a dozen different compilers I've thrown at it so far.
Its a good feeling.