From: Tommy Reynolds <reynolds@redhat.com>
To: Luben Tuikov <luben@splentec.com>
Cc: root@chaos.analogic.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] coding style addendum
Date: Mon, 10 Mar 2003 16:07:43 -0600 [thread overview]
Message-ID: <20030310160743.76ed3d67.reynolds@redhat.com> (raw)
In-Reply-To: <3E6D096A.1080006@splentec.com>
Uttered Luben Tuikov <luben@splentec.com>, spoke thus:
> References:
> [1] ``The Elements of Programming Style'' by Kernighan
> and Plauger, 2nd ed, 1988, McGraw-Hill.
Keep in mind the date here. Prior to this time, subroutines were the
packaging technique of choice to promote "software reuse": i. e.,
reference the _same_ code in various places throughout a program. K&P
were espousing a fundamental shift in thinking by using subroutines as
functional abstractions. Using your argument that the example code
hides an "implementation", it's difficult to conceive of a code example
that hids neither its data nor its implementation.
I'd suggest an alternate tack:
"When you are deep in the programming 'zone' and code is flowing
from your fingertips and you are amazed at the insight and
understanding evidenced by your code:
STAND UP! MOVE AWAY FROM THE KEYBOARD! GO HOME!
Look at the code again tomorrow and see if it makes any sense to
you then."
next prev parent reply other threads:[~2003-03-10 21:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-10 20:56 [PATCH] coding style addendum Luben Tuikov
2003-03-10 21:32 ` Richard B. Johnson
2003-03-10 21:53 ` Luben Tuikov
2003-03-10 22:07 ` Tommy Reynolds [this message]
2003-03-10 22:30 ` Luben Tuikov
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=20030310160743.76ed3d67.reynolds@redhat.com \
--to=reynolds@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luben@splentec.com \
--cc=root@chaos.analogic.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