Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!panda!talcott!harvard!seismo!brl-tgr!tgr!richw%ada-uts.uucp@BRL.ARPA
From: richw%ada-uts.uucp@BRL.ARPA
Newsgroups: net.lang.c
Subject: Re: \"handy.h\"
Message-ID: <1339@brl-tgr.ARPA>
Date: Sat, 7-Sep-85 16:05:44 EDT
Article-I.D.: brl-tgr.1339
Posted: Sat Sep  7 16:05:44 1985
Date-Received: Mon, 9-Sep-85 04:27:09 EDT
Sender: news@brl-tgr.ARPA
Lines: 22


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