PE>> Most people have stuff that they have done that they have NO
 PE>> intention of selling, so keeping it to yourself when it's no skin off
 PE>> your nose to make it PD is just being a dog in a manger.

 RS> True, but in most cases the problem is the extra effort required to put
 RS> it into an acceptable state, and getting around to doing that. Not a
 RS> deliberate desire to be a prick.

Well I should add to that, "release it even if it isn't into a
perfectly desirable state, people can add to it".  Once some of these
guys start using PKT2QWK (which I have read some of the code so that I can
tell them what options to use), I'm sure I can bully them into writing up
some docs for it.

 PE>> Whereas if you put something into the PD (it doesn't have to be a
 PE>> program, a short story or recipe or song or practically anything will
 PE>> do), you know that you have advanced the state of the world FOREVER.

 RS> Only if its built on. Much never is.

Agreed.  It basically has to have an interface that is clean enough that it
takes less time to figure out their interface than it does to write your
own. I personally have put my money on an interface spec like ISO C has. 
Do you have any other suggestions on making code reusable?  I would also
suggest it needs a standard error-handling strategy, like I have supplied
with error.c.

 PE>> The technology you provide can NEVER be destroyed, because it will be
 PE>> spread to BBS's all over the world.

 RS> And much of it disappears very quickly.

I think my hard disk will be able to keep all Public Domain C source code. BFN.

Paul

--- GoldED/2 2.42.G1114