Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!ames!ucbcad!ucbvax!jade!lapis.berkeley.edu!oster
From: oster@lapis.berkeley.edu.UUCP
Newsgroups: comp.windows.x
Subject: Re: Long names in System V
Message-ID: <3059@jade.BERKELEY.EDU>
Date: Mon, 6-Apr-87 14:31:35 EST
Article-I.D.: jade.3059
Posted: Mon Apr  6 14:31:35 1987
Date-Received: Fri, 10-Apr-87 00:29:21 EST
References: <040187.111854.dan@ibm.com> <311@desint.UUCP> <776@jumbo.dec.com> <16197@sun.uucp>
Sender: usenet@jade.BERKELEY.EDU
Reply-To: oster@lapis.berkeley.edu (David Phillip Oster)
Organization: University of California, Berkeley
Lines: 20

In article <16197@sun.uucp> shannon@sun.uucp (Bill Shannon) writes:
>How about chk_msk_ev.c for the filename and x_chk_msk_ev() for the
>function name?  I find it quite painful to visually parse a bunch
>of letters into words using only case change to separate the words.

On the contrary:
The underscore as a word separator has its origin in systems with a
limited character set: no upper and lower case, just upper case and
underscore.
I find it quite painful to read and write names using the underscore as
separator. For me, ChkMskEv.c is much easier to read then chk_msk_ev.c.
The extra length of the latter form also gets on my nerves.  After all,
these things are _names_ not _sentences_ (limited character set: here I
mean switch to italic font style.)

What we really need are systems powerful enough to put names into our
personal canonical forms when we type them, and when the system shows them
to us. Not only in our editors but also on our command lines and in our
debuggers. A canonical form reader/printer would also solve the problem
that the Lisp people have with the C style names of X.