[lwip-users] RE:Re: [lwip] The future of lwIP

[Paul Sheer]

------=_Part_758_738219.1029783959027
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

> where developers disagree, what happens?

 "There is always one best way of doing things.
 If we can't agree it means that no one knows
 what that best way is." - me

> [...] when you start using them to switch 
> between radically different code structures it can
> get very messy and hard to maintain.

hmmmm

If there are radically different code structures
then these can go in a separate file, and be part
of a different make configuration.

I think our work should be to *find* a way
to make things clean.

> I'd much rather see it remain a generic stack, and 
> have people add their own refinements.

I do understand the vision

but remember that LwIP as it is *not* usable
because of numerous errors in the memory
allocation.

I have fixes for all these bugs, but I cannot
easily keep my code in sync for the reasons
you stated.

it would really be quite clean to macro-ize
some of the infrustructure to help those
like me.

Has anyone else has audited lwIP with
two completely seperate memory tracer
packages and TWO MONTHS of continuous
loading? My work may go to waist.

-paul




Powered by World Online - http://www.worldonline.co.za



------=_Part_758_738219.1029783959027--

[This message was sent through the lwip discussion list.]