Thanks Imm, Didn't realize I was in the presence of a lore master..... I'll check the link.
What is the best way to make sure my code is clean? Thanks, Marty imm <[EMAIL PROTECTED]> wrote: On 28 Nov 2007, at 20:04, marty moore wrote: > By OS cleanup, do you mean that gnome cleans up all of the > leftovers, or does Linux clean things up? > > What subject can I search in the archives to learn more? I've > looked at the postings under destructors. This comes up fairly frequently in this list - we get a lot of folk who have been taught the you *have* to delete everything you new, and panic when fluid doesn't.... Anyway, I think the most recent version (prior to this) was around about, lets see... 17th Nov... http://www.fltk.org/newsgroups.php?gfltk.general+v:24045 That might give you a bit of background into why things are the way they are. > Should I ignore valgrind leak reports? Not at all, but it is very tricky to fully comprehend what they really mean, particularly in the entry and exit cases, and at the boundaries. However, there are a few folk around here who have studied hard the lore of the ancients, and they tell us that fltk is clean. Which is not to say that any program written with fltk *must* be OK, we can all make mistakes, but fltk itself should be fine! _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk --------------------------------- Never miss a thing. Make Yahoo your homepage. _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
