>
>...skipping all the off-topic gripes...
I agree, they were off topic. I was just indicating that there are other
problems that are facets of the same problem you are mentioning -
ie a "clear decision from MySQL, Inc. to seriously maintain the XXX as
they currently claim to, or to give it up to someone who will" is required
for a range of XXX, not just the C++ API.
Given that is they case, they are unlikely to do EITHER for the C++ API (ie
do it properly, or officially give it up).
So what do you suggest for the C++ API if that is the case? (or are you
more optimistic than me?)
Ian
> > Given the commercial nature of the mysql project (those license fees
> > must be adding up by now)
>
>If they don't want to use their revenue to pay for C++ API development,
>that's fine with me. All I want out of this thread is a clear decision
>from MySQL, Inc. to seriously maintain the API as they currently claim to,
>or to give it up to someone who will.
