public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Larry McVoy <lm@bitmover.com>
To: Jonathan Earle <jearle@nortelnetworks.com>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [OT?] Coding Style
Date: Tue, 23 Jan 2001 07:58:05 -0800	[thread overview]
Message-ID: <20010123075805.A2575@work.bitmover.com> (raw)
In-Reply-To: <28560036253BD41191A10000F8BCBD116BDCCD@zcard00g.ca.nortel.com>
In-Reply-To: <28560036253BD41191A10000F8BCBD116BDCCD@zcard00g.ca.nortel.com>

On Tue, Jan 23, 2001 at 10:41:49AM -0500, Jonathan Earle wrote:
> I prefer descriptive variable and function names - like comments, they help
> to make code so much easier to read.
> 
> One thing I wonder though... why do people prefer 'some_function_name()'
> over 'SomeFunctionName()'?  I personally don't like the underscore character
> - it's an odd character to type when you're trying to get the name typed in,
> and the shifted character, I find, is easier to input.

I have a tendency to use class_functionName() where "class" represents a
class of related functions.  They all tend to take a point to an instance
of that "class".  So then you can read the code and see the "classes" in
the names.

And, this way, I can piss off both the anti underscore and the anti mixed case
people at the same time :-)
-- 
---
Larry McVoy            	 lm at bitmover.com           http://www.bitmover.com/lm 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-01-23 15:58 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-23 15:41 [OT?] Coding Style Jonathan Earle
2001-01-23 15:58 ` Larry McVoy [this message]
2001-01-23 16:00 ` Mike Harrold
2001-01-23 16:14   ` Georg Nikodym
2001-01-23 18:05     ` Christopher Friesen
2001-01-23 18:41       ` Mathieu Chouquet-Stringer
2001-01-23 18:44       ` Georg Nikodym
2001-01-23 18:53     ` James Kelly
2001-01-23 16:32   ` Joe deBlaquiere
2001-01-24  1:14     ` Steve Underwood
2001-01-25 13:33       ` Kai Henningsen
2001-01-24  5:42     ` Brent Rowland
2001-01-24  5:50       ` Andre Hedrick
2001-01-24  9:58   ` Completely offtopic : " Bernd Petrovitsch
2001-01-25 13:25   ` Kai Henningsen
2001-01-25 19:30     ` Harald Arnesen
2001-01-26  0:20     ` James Stevenson
2001-01-23 17:42 ` John Kodis
2001-01-25 13:38   ` Kai Henningsen
  -- strict thread matches above, loose matches on Subject: below --
2001-01-23 22:22 Jonathan Earle
2001-01-23 16:47 Jesse Pollard
2001-01-24  0:07 ` Stephen Satchell
2001-01-22 21:09 Stephen Satchell
2001-01-22 16:42 ` Mark I Manning IV
2001-01-22 23:56 ` Anton Altaparmakov
2001-01-23  0:01   ` Larry McVoy
2001-01-23  6:37 ` Stephen Satchell
2001-01-23  8:37 ` Helge Hafting
2001-01-23 18:58   ` Alan Olsen
2001-01-22 17:53 Jonathan Earle
2001-01-22 16:04 Jonathan Earle
2001-01-22 16:19 ` Mike Harrold
2001-01-22 16:22 ` Larry McVoy
2001-01-22 18:29   ` Richard B. Johnson
2001-01-22 23:20   ` Admin Mailing Lists
2001-01-23  0:54     ` Werner Almesberger
2001-01-23 12:28   ` Steve Underwood
2001-01-23 16:17     ` Nicolas Noble
2001-01-23 21:16       ` David Benfell
2001-01-23 12:52   ` Andrew Morton
2001-01-23 18:10   ` Stephen Satchell
2001-01-22 17:43 ` Gregory Maxwell
2001-01-20 15:32 Anton Altaparmakov
2001-01-20 16:19 ` [OT?] " profmakx.fmp
2001-01-21  5:10   ` Ragnar Hojland Espinosa
2001-01-21  5:50     ` Admin Mailing Lists
2001-01-21  5:58       ` Mike A. Harris
2001-01-21  7:07         ` Josh Myer
2001-01-21  7:20       ` Alan Olsen
2001-01-21 22:40       ` Mo McKinlay
2001-01-22  0:23         ` Admin Mailing Lists

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=20010123075805.A2575@work.bitmover.com \
    --to=lm@bitmover.com \
    --cc=jearle@nortelnetworks.com \
    --cc=linux-kernel@vger.kernel.org \
    /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