Aaron Stone wrote:
Hey folks,
Dan and Hans have been working on locating memory leaks the past few days. The
culminating event has been Dan's work on adding garbage collection to DBMail.
I really don't want to shoot you guys down on this one, I like the idea of
moving to a future with GC and memory pools and all sorts of useful stuff...
just that I've really put my butt on the line with this temporary thaw thing,
and I *really* don't want to see it go on a single minute longer than is
needed to fix the specific items that we identified last week and which I
talked most people into believing were worth fixing with breakage before the
2.0 release.
Basically, I think it's a bad idea to change the memory management scheme
right before a release. That might sound funny given that I've been advocating
for lots of other breakage before the release, but my thinking is that memory
leaks and even GC are internal issues which can be changed during the stable
series without disrupting how people and other software interacts with DBMail.
Dan, Hans, defenses for garbage collection? Thoughs, questions, comments?
I have absolutely no intention to put garbage collection in the next
DBMail release. Maybe after that (although we probably need some good
discussions about it.. ;) )
For the moment, I'm quite happy fixing the memleaks Hans has found. We
should not make any changes to the memory handling now, only fix some
obvious bugs. I'm not going to search for anymore of them, we'll fix
them as we go along (before or after release).
Ilja
--
Ilja Booij
IC&S B.V.
Stadhouderslaan 57
3583 JD Utrecht
www.ic-s.nl
T algemeen: 030 6355730
T direct: 030 6355739
F: 030 6355731
E: [EMAIL PROTECTED]
