Re: bugfixes

[Kasper Peeters <t16@nikhef.nl>]

> So, I would suggest just freezing the code now to find the bugs in
> it.  I kept ignoring all the segfaults, because I was using the
> test_net program which works nicely.

Ok, freezing right now is fine with me as well if you think there
are too many conceptual problems still to be solved. In that case,
we should decide what CVS version to start from.

> In terms of debugging, I would suggest working on replacing some of the
> memory management stuff with things like a Buffer class for the filter
> stacks, etc.  Things that will replace the old broken schemes instead of
> fixing them.

That was the idea behind writing coding guidelines at the same time.
Clean up everything to be consistent in using STL containers, the use
of pointers vs. references and so on. 

> Why?  Maybe limit the actual people who can commit changes to the tree,
> but no reason not to declare open season on bugs and have anyone hunt them
> down and post results to mailing list :)

I was saying that because most bugs probably have to do with more than
just one isolated part of the code. If everyone starts to hunt down
his favourite bug, we'll be duplicating a lot of work. It's not very
easy to put person X on fixing the bugs in directory Y at this stage.
I would suggest that a few people start to fix the more obvious bugs
first, commit those fixes to CVS, and then ask the other people to
help out with the nasty ones.

Kasper