2008/6/18 Rene Gollent <anevilyak@xxxxxxxxx>: > On Wed, Jun 18, 2008 at 6:34 AM, Salvatore Benedetto <emitrax@xxxxxxxxx> > wrote: >> >> Hmm.. then why the destructor is called? >> > > For something that's allocated on the stack, the destructor is called > automatically when the object goes out of scope (which is to say, we > exit the function). If that's not what you're seeing, do you have the > full trace somewhere? Yep, at first I didn't think that Index::SetTo() could get to the end and I thought that the destructor would actually be called because the constructor failed, but I was obviously wrong. Regards, -- Salvatore Benedetto (a.k.a. emitrax) Student of Computer Engineer University of Pisa www.haiku-os.it