From: Joe deBlaquiere <jadb@redhat.com>
To: Mike Harrold <mharrold@cas.org>
Cc: Jonathan Earle <jearle@nortelnetworks.com>,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [OT?] Coding Style
Date: Tue, 23 Jan 2001 10:32:52 -0600 [thread overview]
Message-ID: <3A6DB234.1090507@redhat.com> (raw)
In-Reply-To: <200101231600.LAA24562@mah21awu.cas.org>
Too bad we can't just do a "Prince" and invent unpronouncable symbols to
use as function names... or perhaps just use something from the chinese
fonts ;o)...
Mike Harrold wrote:
>> This message is in MIME format. Since your mail reader does not understand
>> this format, some or all of this message may not be legible.
>>
>> ------_=_NextPart_001_01C08552.FFC336D0
>> Content-Type: text/plain;
>> charset="ISO-8859-1"
>>
>> 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.
>>
>
>
> For exactly the reverse of that reason. Typing capital letters is a heck
> of a lot more difficult that addint an underscore.
>
> Then there is reasability.
>
> void ThisIsMyDumbassFunctionName
>
> if MUCH more difficult to read than
>
> void this_is_my_clear_and_easy_function_name
>
> Regards,
>
> /Mike
>
>
>> Cheers!
>> Jon
>>
>>
>>> -----Original Message-----
>>> From: Steve Underwood [mailto:steveu@coppice.org]
>>
>> Some people still seem to be living in the age of K&R C, with 6 or 7
>> character variable names that demand some explanation. Maybe some day
>> they will awake to the expressive power of long (and well chosen) names.
>>
>> ------_=_NextPart_001_01C08552.FFC336D0
>> Content-Type: text/html;
>> charset="ISO-8859-1"
>> Content-Transfer-Encoding: quoted-printable
>>
>> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
>> <HTML>
>> <HEAD>
>> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
>> charset=3DISO-8859-1">
>> <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
>> 5.5.2652.35">
>> <TITLE>RE: [OT?] Coding Style</TITLE>
>> </HEAD>
>> <BODY>
>>
>> <P><FONT SIZE=3D2>I prefer descriptive variable and function names - =
>> like comments, they help to make code so much easier to read.</FONT>
>> </P>
>>
>> <P><FONT SIZE=3D2>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.</FONT></P>
>>
>> <P><FONT SIZE=3D2>Cheers!</FONT>
>> <BR><FONT SIZE=3D2>Jon</FONT>
>> </P>
>>
>> <P><FONT SIZE=3D2>> -----Original Message-----</FONT>
>> <BR><FONT SIZE=3D2>> From: Steve Underwood [<A =
>> HREF=3D"mailto:steveu@coppice.org">mailto:steveu@coppice.org</A>]</FONT>=
>>
>> </P>
>>
>> <P><FONT SIZE=3D2>Some people still seem to be living in the age of =
>> K&R C, with 6 or 7</FONT>
>> <BR><FONT SIZE=3D2>character variable names that demand some =
>> explanation. Maybe some day</FONT>
>> <BR><FONT SIZE=3D2>they will awake to the expressive power of long (and =
>> well chosen) names.</FONT>
>> </P>
>>
>> </BODY>
>> </HTML>
>> ------_=_NextPart_001_01C08552.FFC336D0--
>> -
>> 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/
>>
>
>
> -
> 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/
--
Joe deBlaquiere
Red Hat, Inc.
307 Wynn Drive
Huntsville AL, 35805
voice : (256)-704-9200
fax : (256)-837-3839
-
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/
next prev parent reply other threads:[~2001-01-23 16:33 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
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 [this message]
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=3A6DB234.1090507@redhat.com \
--to=jadb@redhat.com \
--cc=jearle@nortelnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mharrold@cas.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