public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: Robert Love <rml@tech9.net>,
	Rusty Russell <rusty@rustcorp.com.au>,
	torvalds@transmeta.com, linux-kernel@vger.kernel.org,
	akpm@zip.com.au
Subject: Re: [TRIVIAL PATCH] Remove list_t infection.
Date: Sun, 1 Sep 2002 23:27:38 -0700	[thread overview]
Message-ID: <20020902062738.GP888@holomorphy.com> (raw)
In-Reply-To: <15731.1019.581339.120099@notabene.cse.unsw.edu.au>

On Sunday September 1, wli@holomorphy.com wrote:
>> Seconded. Throw the whole frog in the blender, please, not just half.

On Mon, Sep 02, 2002 at 04:23:55PM +1000, Neil Brown wrote:
> The struct in question is a handle on an element of a list, or the
> head of a list, but it is not a list itself.  A list is a number of
> stuctures each of which contain (inherit from?)  the particular
> structure.  So calling it "struct list" would be wrong, because it
> isn't a list, only part of one.
> Maybe "struct list_element" or "struct list_entry" would be OK.  But
> I'm happy with "struct list_head", because the thing is, at least
> sometimes, the head of a list.

Why bother? It's obvious what it is, and the debate weighs more in terms
of bickering over what the most descriptive possible term is than all the
supposed fluff in terms of diffsize. Just give it an obvious name that
doesn't require so many extraneous characters to type and rest assured
in that this of all things is too obvious to mistake for anything else.
This much time and effort isn't useful to spend explaining or messing with
something as trivial as lists. Let names be short and kill the typedef.

Cheers,
Bill

  parent reply	other threads:[~2002-09-02  6:28 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-02  5:23 [TRIVIAL PATCH] Remove list_t infection Rusty Russell
2002-09-02  5:51 ` Robert Love
2002-09-02  6:02   ` William Lee Irwin III
2002-09-02  6:20     ` David S. Miller
2002-09-02 10:11       ` Daniel Phillips
2002-09-02 10:05         ` David S. Miller
2002-09-02 10:16           ` Daniel Phillips
2002-09-02 10:11             ` David S. Miller
2002-09-02 10:25               ` Daniel Phillips
2002-09-02 10:21                 ` David S. Miller
2002-09-02 10:24           ` William Lee Irwin III
2002-09-03 22:13           ` Jamie Lokier
2002-09-03 23:14             ` Linus Torvalds
2002-09-04  0:41               ` Rusty Russell
2002-09-04  1:52                 ` Daniel Phillips
2002-09-04  2:26                   ` Linus Torvalds
2002-09-04  2:44                     ` Rusty Russell
2002-09-04 14:36                       ` J.A. Magallon
2002-09-04  6:11                   ` Thunder from the hill
2002-09-02  6:23     ` Neil Brown
2002-09-01 20:45       ` Nick Piggin
2002-09-02  6:27       ` William Lee Irwin III [this message]
2002-09-02 10:07       ` Daniel Phillips
2002-09-02 10:05     ` Daniel Phillips
2002-09-02  6:17   ` Rusty Russell
2002-09-06  9:28 ` Dan Aloni
2002-09-06 14:35   ` Robert Love
2002-09-09  5:57   ` Rusty Russell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020902062738.GP888@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    --cc=rml@tech9.net \
    --cc=rusty@rustcorp.com.au \
    --cc=torvalds@transmeta.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox