Jeff Garland wrote:
I'd still really like to see a database binding library make it into TR2. Not having this is killing C++ against Java for application developers. We've had some periodic fits and starts, but it seems clear we won't have a Boost library by then. I'd still like to see someone with some time step up and take this on. It's been done about 10 times so I think a proposal could be gleaned from the best of the current bindings...
All this database talks made me a bit puzzled. What's exactly the standard committee can do about database interface? I mean, does specifying a standard interface for database means that I can write code that uses this interface and then I'll find my self reading data from a database? Which database? The database compiler vendors will suddenly have to provide with their compiler to satisfy the standard requirements? Probably not... Compiler vendors won't start writing databases (except Microsoft, of course :-) ). This means that this standard interface would be directed to database vendors rather than compiler vendors. Is this the plan? That database vendors will start supplying C++ header files and lib files with a "C++ Compliant" stamp? Just thinking out loud... Yuval