List available library user space functions with descriptions. 2047

Obviously, there are general libraries that see a lot of use and the documentation is easy to find.

But, a library is just a collection of useful routines. One can just as easily code those routines into the main program. The disadvantage being that it's not as easy to reuse in other programs, and there's now way to share that code amongst more than one program running at the same time (which results in more space being used).

I think what you'll find is that after those really general libraries, there is a sharp drop-off in commonality of the other libraries. One programmer may put some routines into a library when writing a program because they personally want to reuse the routines. Someone else may feel there is more demand for the routines than turns out to be the case. Someone else may want to bring some new standards in an area, and hopes that by putting the routines in a library they will get better propagation. Or, someone simply thinks a routine is too good to get lost in some other program, so they put it in a libary; there may not be much demand for such a routine (because few have actual use for that function) but it turns out to be a really good routine for those who actually need it.

The result is that there are libraries that see very little use beyond the program they are commonly attached to.

Remember, each program is the product of the person writing it. They obviously have to match some standards to be compatible with everything else, and some standards if they hope for much propagation, but they are not feeding it into some central bureaucracy where it is mashed into some set of standards and cleaned up. The documentation reflects the effort of the program writer, and even reflects their intent on the useage of the program or who they expect to use it. They may not see much use in documenting a library that won't see much use.

So it seems like you want all those libraries documented because you buttume there is lots of useful routines in them. That may be the case. But once beyond the common routines in the common libraries, much of it will likely be only for highly specific uses.

So perhaps it's better not to try to look for useful things, and then write a program around them. It might be better, when stuck with the need for some routine, doing searches for something suitable. Then the search work only comes up when you need it.

Michael