From: Warren Young
Date: January 9 2010 1:02am
Subject: Re: mysqlpp::ScopedConnection
List-Archive: http://lists.mysql.com/plusplus/8847
Message-Id: <4B47D5AA.2060706@etr-usa.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 1/8/2010 3:20 AM, Joel Fielder wrote:
>
> but it also provides operator->() so you can treat it as if it were a
> pointer to a Connection.

You might try to get Jonathan Wakely's attention on it, then.  He's the 
local authority on smart pointers, and he had a fair bit to do with 
ConnectionPool, too.

> Would you like a patch?

If you want to donate the class under the LGPL, it sounds like something 
we'd like to have in MySQL++.

> If so, where would be an appropriate place in the library

In general, I prefer to keep each class in its own module, named after 
the class, abbreviated only if the full name would be long.  You might 
therefore call it 'scopedconn'.  The only exception is when a thing is 
very small (double-digit SLOC) and especially when it's closely related 
to other classes in the same module.  See the exceptions and 
manipulators, for example.