On 11/25/2009 04:32 PM, Leif Hedstrom wrote:
I'd suggest we come up with a list of the requirements for what needs to be done in the "2.x" branch, and then freeze it. I'd be hard to convince that addressing the issues listed above is not one of those requirements :).
I should say, changing APIs to be C++ is definitely not on my personal "requirements" list, but I'm open to the ideas. You know me, I'm not much of a C++ "biggot" in any way (me and templates don't go well together). If we decide that changing APIs to C++ can wait until a (much) later 3.0 release, than I'm totally fine with that (or, even canning the idea of C++ APIs as well, I just don't really feel strongly either way). There might be bigger fishes to fry honestly, like you say, getting a stable release is definitely one of them (but, I still think we need to examine the existing APIs, and fix that which is missing or outright broken).
Cheers, -- leif
