C++0x

So C++0x, that rough beast, slouches toward... well, nowhere in particular, still. At this point it does indeed look like the 0x on the end will be a hexadecimal prefix; there are simply too many issues to address before the October meeting in Santa Cruz.

I was amused to note that the Chinese and Canadian responses to the N2800 draft consisted of only two comments each, and in both cases one was simply an adjuration to the committee to 'consider' (CA) or 'address' (CH) the 187 open issues. (In the wake of the hundreds of other comments from the UK [344], the US [98], Japan [81], and others [less], the open issues now number 327, with a fair number of issues raised that have not yet been assigned defect numbers). I was further amused to note that, while China's other comment did concern a relevant, highly technical issue (and one which I'd run into myself, at that), it had nothing to do with C++0x; it's actually been around since C++98. (And I suspect it'll get pushed off to revision-after-0x, too.)

(N2800 has since been superseded by N2857, if you're interested, although it'd probably be easier to read the proposals named here and/or the papers submitted here, instead.)