From: <profmakx.fmp@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [OT?] Coding Style
Date: Sat, 20 Jan 2001 17:19:17 +0100 (MET) [thread overview]
Message-ID: <19160.980007557@www16.gmx.net> (raw)
In-Reply-To: <5.0.2.1.2.20010120152158.00ab7bc0@pop.cus.cam.ac.uk>
Hi
I just wanted to say that Linus´ CodingStyle is the ONLY SANE style of
writing code in bigger projects. At university we are forced to use exactly the
braindamaged settings and styles that linux condemns. So, every good programmer
should know where to put comments. And it is unnecessary to put comments to
explain what code does. One should see this as stated in the CodingStyle doc.
Ok, there are points where a comment is good, but for example at university
we are to comment on every single line of code ...
So back to work now!
Markus
--
Sent through GMX FreeMail - http://www.gmx.net
-
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-20 16:19 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.10.10101192217390.9361-100000@penguin.transmeta .com>
[not found] ` <3A68E309.2540A5E1@purplecoder.com>
2001-01-20 6:29 ` Coding Style Linus Torvalds
2001-01-20 15:32 ` Anton Altaparmakov
2001-01-20 16:19 ` profmakx.fmp [this message]
2001-01-21 5:10 ` [OT?] " 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
2001-01-21 8:24 ` george anzinger
2001-01-22 16:04 [OT?] " 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-22 17:53 Jonathan Earle
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-23 15:41 Jonathan Earle
2001-01-23 15:58 ` Larry McVoy
2001-01-23 16:00 ` Mike Harrold
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-26 0:20 ` James Stevenson
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 17:42 ` John Kodis
2001-01-25 13:38 ` Kai Henningsen
2001-01-25 13:25 ` Kai Henningsen
2001-01-25 19:30 ` Harald Arnesen
2001-01-23 16:47 Jesse Pollard
2001-01-24 0:07 ` Stephen Satchell
2001-01-23 22:22 Jonathan Earle
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=19160.980007557@www16.gmx.net \
--to=profmakx.fmp@gmx.de \
--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;
as well as URLs for NNTP newsgroup(s).