Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site cyb-eng.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!ut-sally!oakhill!cyb-eng!bc
From: bc@cyb-eng.UUCP (Bill Crews)
Newsgroups: net.lang.c
Subject: Re: long names in 'C' programs
Message-ID: <559@cyb-eng.UUCP>
Date: Thu, 30-May-85 23:14:35 EDT
Article-I.D.: cyb-eng.559
Posted: Thu May 30 23:14:35 1985
Date-Received: Mon, 3-Jun-85 04:29:06 EDT
References: <476@aicchi.UUCP> <668@mcvax.UUCP> <964@peora.UUCP> <190@geowhiz.UUCP>
Organization: Cyb Systems, Austin, TX
Lines: 42

>It's simply an issue of compatibility.  Unless you want to make your users
>suffer unnecessarily, you should introduce new changes gradually, and wait
>for the old ones to die out gracefully, rather than forcing new features
>on the user.

This feud has no possibility of being won, so long as the feuders continue to
ignore the fact that contexts exist within which software development is
performed.  In some cases, programs are written intentionally to be quick and
dirty (and, hopefully, throw-away).  Local idioms would be called for if the
development process is accelerated or made more reliable.  Others publish
software with which source code is distributed.  Understandability would seem
to be the key here.  Still others develop source code which will likely be
hacked into various forms and run on many different systems during its life.
Perhaps in this case some understandability should be sacrificed for greater
portability.

By defining the realm of his concern to be COMPATIBILITY, the author has set
his context, and the conclusions are obvious.  But surely he doesn't believe
that portability is the only consideration in the development of programs!

I fall in the category of "long namers" because the bulk of the work I do
involves large systems in which parts are written by various programmers
who would have a difficult time repeatedly having to figure out what is meant
by such variable names as bufav or even pktwait, when buffer_available and
packet_waiting tell one just what is the meaning of the variable.  On such
projects, I must often reread and remember what *I* wrote several months
earlier.

But if I were writing code that only I read or maintained, which took only
a few days to write, and which did not relate to external modules much, I
would probably adopt a different style.

Please try not to judge everyone else by your own circumstances and even
prejudices.

-- 

  /  \    Bill Crews
 ( bc )   Cyb Systems, Inc
  \__/    Austin, Texas

[ gatech | ihnp4 | nbires | seismo | ucb-vax ] ! ut-sally ! cyb-eng ! bc