Mailing List
Home
Forum Home
MySQL General - General MySQL discussion
MySQL++ - Programming with the C++ API to MySQL
MaxDB - Everything about MaxDB, formerly known as SAP DB
ODBC - ODBC with the MySQL Connector/ODBC driver
MySQL on Win32 - Runing MySQL on Windows 9x/Me/NT/2000/XP
Java Help - Mostly related to the MySQL Connector/J driver
Perl - Perl support for MySQL with DBI and DBD::mysql
GUI - MySQL GUI Tools
Announcement
Subjects
mysql openssl Question
ERROR 1045: Access denied for user: 'root@localhost ' (Using
password: NO)
Update one field with more fields from another table
Getting Identity after INSERT
ERROR 2002: Can 't connect to local MySQL server through socket
mysql test 4 1 fails with the gis test
MySQL Cluster Software
Downgrade Mysql from 4 to 3 23
Mysql 4 0 Oracle Stored Procedure Trigger Conversion
Can 't access mysql after kernel upgrade
Executing MySQL Commands From Within C Program
Comparing and writing out BLOBS
Preventing Duplicate Entries
FULLTEXT query format question
Strange behavior, Table Level Permission
Does the binary log enabling affect the MySQL performances?
mysql:it 's a db not a dbms how it 's possible?!
mysql have same function mthod as Oracle decode()
 
-none-

-none-

2007-08-15       - By Chris Frey

 Back
On Wed, Aug 15, 2007 at 12:27:18AM -0600, Warren Young wrote:
> Smart pointers are tricky, and automatic memory management is even
> trickier, and I just created a template that does both.  I swapped it in
> for existing code in MySQL++ that used value semantics and it passes the
> test suite, but I'd still appreciate someone else taking a look at it.
>
> http://svn.gna.org/viewcvs/mysqlpp/trunk/lib/refcounted.h?view=markup

Just some nit-pick comments. :-)

  void assign(T* c)
  {
    detach();

    if (c) {
      counted_ = c;
      refs_ = new size_t(1);
    }
    else {
      counted_ = 0;
      refs_ = 0;
    }
  }


In a very rare case, the call to:

  assign(new SomeObject);

will leak memory if the new size_t(1) runs out of memory and throws an
exception.

Also, I'm more paranoid, and would probably zero the pointers in
detach() anyway, just in case of that new exception.

Although if new throws, we have bigger problems to worry about. :-)
I usually don't even bother catching out of memory exceptions.  But
a library probably shouldn't leak, in case there are people who do
catch out-of-mem.

- Chris


--
MySQL++ Mailing List
For list archives: http://lists.mysql.com/plusplus
To unsubscribe:    http://lists.mysql.com/plusplus?unsub=mysql@(protected)