Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: $Revision: 1.6.2.16 $; site ada-uts.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!ada-uts!richw
From: richw@ada-uts.UUCP
Newsgroups: net.lang.c
Subject: Re: "handy.h"
Message-ID: <10200007@ada-uts.UUCP>
Date: Tue, 3-Sep-85 11:11:00 EDT
Article-I.D.: ada-uts.10200007
Posted: Tue Sep  3 11:11:00 1985
Date-Received: Sat, 7-Sep-85 07:11:30 EDT
References: <10200006@ada-uts.UUCP>
Lines: 22
Nf-ID: #R:ada-uts:10200006:ada-uts:10200007:000:883
Nf-From: ada-uts!richw    Sep  3 11:11:00 1985


>> 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