David Murn writes:
>
> On Fri, 29 Jan 1999, Gaurav Lochan wrote:
>
> > About ELKS, well, i wanted to know WHY you havent been able to write a
> > TCP/IP stack for it ?
>
> To start with, there IS the beginnings of a TCP/IP stack. I think the
> author managed to get it to reply to pings, but I'm not sure if he did or
> not. The big problem is that we're very tight on memory space, so the
> code has to be small.
>
TCP/IP stacks under ELKS have so far clearly demonstrated the benefit of
sharing code, and releasing early in on Open Source project. At least two
people working on code for the project for a while by themselves, have lost
their own copies and then given up rather than starting again from scratch.
A plea to anyone working on code for the project:
It doesn't matter how broken or buggy your code is. The sooner you share it
with the list the better. The more bugs in the code, the more likely it is
that someone else will fix the bug. Everyone else will then backup your
code for you by downloading it, and interest will be stimulated in what you
are doing and the project in general.
I know it is very tempting to sit on your code for a long time. It can be
embarrasing to release code with bugs in. I know this from experience, but
many eyes spot bugs far more quickly than two can.
Al
