\"handy.h\"

[richw%ada-uts.uucp at BRL.ARPA]

>> I'm interested in coming up with an include file, say "handy.h",
>> -- Rich Wagner

> If people, when choosing names for functions, variables, files, etc, would
> think at least briefly about what name would be the most meaningful to an
> uninitiated reader, we readers would have a much easier time.  I would
> suggest you come up with names like types.h or ctlchars.h or whatever,
> segregate them functionally and name them appropriately.
> -- Bill Crews

"segregate them functionally" -- I'm impressed  :-)

Now that you mention it, you've got a point.  I originally didn't expect
as many responses as I've gotten, so it will make sense to create several
files (can you say ``modularity''?).

Now, can we get back to the original question?  Thanks to the replies
I've gotten via e-mail -- a (personally edited; sorry) listing of
``good stuff'' will be posted soon...

-- Rich