On Fri, Jul 27, 2012 at 03:42:57PM +0100, Simon Davies scratched on the wall:
> On 27 July 2012 15:22, Arbol One <arbol...@gmail.com> wrote:
> > Before calling the destructor, I would like to make sure that all the
> > sqlite3_stmt have been 'finalized', is there a function in SQLite that that
> > can help me do this, or should I just use 'NULL'?
> 
> The documentation is there to help you...
> http://www.sqlite.org/c3ref/next_stmt.html
> http://www.sqlite.org/c3ref/finalize.html

  That's what you want.  Of course, finding an unfinalized statement is
  really something of an error condition.   It means your application
  lost track of something, and failed to free a dependent resource.
  Having your object blindly finalize statements is very likely to
  leave a dangling pointer elsewhere in the application.

   -j

-- 
Jay A. Kreibich < J A Y  @  K R E I B I.C H >

"Intelligence is like underwear: it is important that you have it,
 but showing it to the wrong people has the tendency to make them
 feel uncomfortable." -- Angela Johnson
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to