Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!lll-lcc!pyramid!oliveb!sun!shannon
From: shannon@sun.UUCP
Newsgroups: comp.windows.x
Subject: Re: Long names in System V
Message-ID: <16197@sun.uucp>
Date: Mon, 6-Apr-87 00:12:59 EST
Article-I.D.: sun.16197
Posted: Mon Apr  6 00:12:59 1987
Date-Received: Wed, 8-Apr-87 04:21:23 EST
References: <040187.111854.dan@ibm.com> <311@desint.UUCP> <776@jumbo.dec.com>
Organization: Sun Microsystems, Inc. - Mtn View, CA
Lines: 16

In article <776@jumbo.dec.com>, jg@jumbo.dec.com (Jim Gettys) writes:
> I find it easier to parse names of files if there is some way to tell where
> one word begins and ends.  This is particularly important once you have
> abbreviated file names to live within 12 characters.  For example,
> XChkMskEv.c I find easier to deal with than xchkmskev.c would be.

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.
And I find it a real pain to type such names!

The mixed case hack is a leftover from languages with restricted
character sets.  C has a reasonable word separator (underscore), why
not use it?

					Bill Shannon