From: john slee <indigoid@higherplane.net>
To: Jonathan Earle <jearle@nortelnetworks.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Coding Style
Date: Wed, 24 Jan 2001 14:23:14 +1100 [thread overview]
Message-ID: <20010124142314.E7426@higherplane.net> (raw)
In-Reply-To: <28560036253BD41191A10000F8BCBD116BDCCB@zcard00g.ca.nortel.com>
In-Reply-To: <28560036253BD41191A10000F8BCBD116BDCCB@zcard00g.ca.nortel.com>; from jearle@nortelnetworks.com on Tue, Jan 23, 2001 at 10:07:10AM -0500
On Tue, Jan 23, 2001 at 10:07:10AM -0500, Jonathan Earle wrote:
> > /*
> > * I tend to find standard C comments easier to read. They stand out,
> > * especially for multiple lines (although I always try to put the :end:
> > * on a separate line for clarity).
> > */
>
> I like this style for multiple line comments, but prefer the '//' for single
> liners. Two less characters to type after all. :)
and potentially no end of weird problems if you have mac users editing
your code... suddenly a compiler may ignore the rest of a file starting
at a given // or # comment, and you'll find its caused by their
different linebreaks. had this problem with php. havent seen it with C
yet. does gcc handle non-correct^H^H^H^H^H^H^Hunix linebreaks now? it
didnt when i used djgpp all those years ago.
// are nicer on the eyes, for short comments. and death to capital
// letters. and oooh, vim auto-extends // comments, thats handy isn't
// it! :-]
j.
-
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-24 3:12 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-23 15:07 Coding Style Jonathan Earle
2001-01-24 3:23 ` john slee [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-06-14 18:48 coding style Cyrill Gorcunov
2007-06-15 4:51 ` Willy Tarreau
2007-06-15 5:09 ` Kok, Auke
2007-06-15 6:38 ` dave young
2007-06-15 6:47 ` debian developer
2007-06-15 6:54 ` dave young
2007-06-15 9:16 ` Jan Engelhardt
2007-06-15 17:32 ` Cyrill Gorcunov
2007-06-15 17:54 ` Chris Friesen
2007-06-15 18:03 ` Randy Dunlap
2007-06-15 19:10 ` Jan Engelhardt
2007-06-15 19:18 ` Cyrill Gorcunov
2007-06-15 19:21 ` Kok, Auke
2007-06-15 19:29 ` Cyrill Gorcunov
2007-06-15 19:31 ` Jan Engelhardt
2007-06-15 19:41 ` Cyrill Gorcunov
2007-06-15 20:21 ` Linus Torvalds
2007-06-15 20:35 ` Jan Engelhardt
2007-06-16 12:30 ` Stefan Richter
2007-06-15 20:21 ` Jan Engelhardt
2007-06-15 20:39 ` Linus Torvalds
2007-06-16 6:38 ` Jan Engelhardt
2007-06-16 12:40 ` Stefan Richter
2007-06-16 15:49 ` Linus Torvalds
2007-06-19 14:05 ` Mark Lord
2007-06-15 19:45 ` Kok, Auke
2007-06-15 19:49 ` Cyrill Gorcunov
2007-06-15 20:28 ` Jan Engelhardt
2007-06-15 22:10 ` Randy Dunlap
2007-06-15 18:05 ` Kok, Auke
2007-06-15 18:22 ` Cyrill Gorcunov
2007-06-16 13:07 ` Stefan Richter
2007-06-16 14:31 ` gorcunov
2007-06-16 17:43 ` Stefan Richter
2007-06-16 18:22 ` Cyrill Gorcunov
2007-06-16 14:22 ` Clifford Wolf
2007-06-15 8:56 ` Krzysztof Halasa
[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-21 8:24 ` george anzinger
2001-01-19 17:59 Mark I Manning IV
2001-01-20 0:09 ` David Ford
2001-01-20 1:26 ` John Cavan
2001-01-20 0:46 ` Albert D. Cahalan
2001-01-20 5:34 ` Linus Torvalds
2001-01-21 2:00 ` Matthias Andree
2001-01-22 8:24 ` Ralf Baechle
2001-01-22 22:28 ` Mark I Manning IV
2001-01-23 3:56 ` adrian
2001-01-23 20:05 ` Boris Dragovic
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=20010124142314.E7426@higherplane.net \
--to=indigoid@higherplane.net \
--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;
as well as URLs for NNTP newsgroup(s).